eonline.com
The domain eonline.com answers at IP address 23.36.162.200. The domain DNS is managed by Akamai, which decides where each subdomain points. Mail for eonline.com goes through 2 servers; the highest priority one is inbound-smtp.us-west-2.amazonaws.com. It also publishes 13 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
A A records
- 23.36.162.200 20s
- 23.36.162.209 20s
MX MX records
- 10 inbound-smtp.us-west-2.amazonaws.com 3600s
- 50 email.eonline.com 3600s
NS NS records
- aus1.akam.net 20221s
- asia2.akam.net 20221s
- asia3.akam.net 20221s
- ns1-102.akam.net 20221s
- use3.akam.net 20221s
- eur3.akam.net 20221s
- ns1-161.akam.net 20221s
- eur4.akam.net 20221s
- usw1.akam.net 20221s
TXT TXT records
- v=spf1 ip:12.46.7.226 -all 99s
- v=spf1 ip:208.78.120.150 -all 99s
- yahoo-verification-key=BA7cyZWD/bUcAWHacbiv/mlU3TAoXO1mVUtdRH+IjhI= 99s
- google-site-verification=HRqGVq6H23RBoZpkjqRgJLFx8SOq9GVxinDBE2A8LFw 99s
- google-site-verification=lL5I6oAU0a5eh4ZS-hLM_iC6cPa32T1eVqTQKBw9i_U 99s
- v=spf1 a:mx0a-00176a04.pphosted.com a:mx0b-00176a04.pphosted.com ip:208.78.120.145 include:aspmx.sailthru.com ~all 99s
- facebook-domain-verification=4ibctlm5ihzdeufrc19auxqcmcctj8 99s
- amazonses:qQ+mkErgudZpnvNGBxI2Zan33i9hBjOhugRT6rS5seo= 99s
- 2rhzbzb6r6p8z5hqxjxwdhw3rd57dgms 99s
- google-site-verification=jOadQCDbZTkKw5sn27yXszjIb9c3PdMPHENN92uPWy8 99s
- a019e5e8a9ff451d9342f0be28384892 99s
- atlassian-domain-verification=GLdM+/NLCFfEabD6ehBftAdFAnqPMwq2xU9TtdxKbIEMPaNDD7sJ8oAxMVye/caJ 99s
- _zavqrou6cwfkug7nq3x143m5kcj8c1l 99s
SOA SOA records
- a1-173.akam.net 3600s
What each record means
- A and AAAA: the server IP address, in IPv4 and IPv6.
- MX: the servers that receive the domain mail. The number is the priority; the lowest is tried first.
- NS: the name servers, which have the final say over the domain DNS.
- TXT: free text. Mostly used for SPF, DKIM and DMARC, and to verify ownership with third parties.
- TTL: how many seconds the record may be cached before asking again.
Checked 3 hours ago.