Your IP: 54.242.8.162 - United States, Woodbridge

DNSreport - ymail.com.

How I am searching:
Searching for ymail.com. record at d.root-servers.net [199.7.91.13]: Got referral to f.gtld-servers.net [took 29 ms]
Searching for ymail.com. record at f.gtld-servers.net [192.35.51.30]: Got referral to ns1.yahoo.com [took 183 ms]
Searching for ymail.com. record at ns1.yahoo.com [68.180.131.16]: Reports ymail.com. [took 35 ms]
CategoryStatusTest nameInformation
ParentPASSParent nameservers have your nameservers listedOK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers.
PASSDNS servers have A recordsOK. All your DNS servers either have A records at the zone parent servers, or do not need them.
INFONS records at parent serversYour NS records at the parent servers are:

ns2.yahoo.com.[68.142.255.16][TTL=172800]
ns4.yahoo.com.[98.138.11.157][TTL=172800]
ns3.yahoo.com.[203.84.221.53][TTL=172800]
ns1.yahoo.com.[68.180.131.16][TTL=172800]
ns5.yahoo.com.[119.160.247.124][TTL=172800]
NSINFONS records at your nameserversYour NS records at your nameservers are:

ns3.yahoo.com.
ns1.yahoo.com.
ns4.yahoo.com.
ns2.yahoo.com.
ns5.yahoo.com.
PASSNo NS A records at nameserversOK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
PASSOpen DNS serversOK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers).
PASSAll nameservers report identical NS recordsOK. The NS records at all your nameservers are identical.
PASSAll nameservers respondOK. All of your nameservers listed at the parent nameservers responded.
PASSNumber of nameserversOK. You have 5 nameservers. You must have at least 2 nameservers.
PASSMissing nameserversOK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
PASSMissing nameservers (reversed)OK. All 5 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
PASSNo CNAMEs for domainOK. There are no CNAMEs for ymail.com.
PASSNo NSs with CNAMEsOK. There are no CNAMEs for your NS records.
PASSNameservers on separate class COK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations.
PASSAll NS IPs publicOK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
PASSTCP AllowedOK. All your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems.
INFONameservers versionsYour nameservers have the following versions:

ns2.yahoo.com. (68.142.255.16): ISC BIND 9.2.3rc1 -- 9.4.0a0
ns4.yahoo.com. (98.138.11.157): ISC BIND 9.2.3rc1 -- 9.4.0a0
ns3.yahoo.com. (203.84.221.53): ISC BIND 9.2.3rc1 -- 9.4.0a0
ns1.yahoo.com. (68.180.131.16): ISC BIND 9.2.3rc1 -- 9.4.0a0
ns5.yahoo.com. (119.160.247.124): ISC BIND 9.2.3rc1 -- 9.4.0a0
SOAINFOSOA recordYour SOA record is:

Primary DNS server: hidden-master.yahoo.com.
Responsible Name: hostmaster.yahoo-inc.com.
Serial: 2014041400
Refresh: 28800
Retry: 3600
Expire: 1814400
Minimum/NegTTL: 600
PASSNS agreement on SOA SerialOK. All your nameservers agree that your SOA serial number is 2014041400.
FAILEDSOA MNAME CheckFAILED. Your SOA (Start of Authority) record states that your master (primary) name server is: hidden-master.yahoo.com. That server is listed at the parent servers, which is not correct.
PASSSOA RNAME CheckOK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: hostmaster@yahoo-inc.com. (techie note: we have changed the initial '.' to an '@' for display purposes).
PASSSOA Serial NumberOK. Your SOA serial number is: 2014041400. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 14 Apr 2014.
PASSSOA REFRESH valueOK. Your SOA REFRESH interval is: 28800 seconds. The normal interval is about 1200-43200 seconds (20 minutes to 12 hours). This value determines how often secondary/slave nameservers check with the master for updates.
PASSSOA RETRY valueOK. Your SOA RETRY interval is: 3600 seconds. The normal interval is about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
PASSSOA EXPIRE valueOK. Your SOA EXPIRE time: 1814400 seconds. The normal interval is about 1209600-2419200 seconds (2-4 weeks). This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
WARNSOA MINIMUM TTL valueWARNING. Your SOA MINIMUM TTL is: 600 seconds. The normal interval is about 3600-10800 seconds (1-3 hours). This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MXINFOMX RecordYour 3 MX records are:

10mta7.am0.yahoodns.net. [TTL=1800]IP=98.136.216.26 [TTL=300]
IP=98.138.112.37 [TTL=300]
IP=66.196.118.36 [TTL=300]
IP=98.138.112.33 [TTL=300]
IP=98.138.112.32 [TTL=300]
IP=98.138.112.34 [TTL=300]
IP=98.136.217.202 [TTL=300]
IP=66.196.118.240 [TTL=300]
10mta5.am0.yahoodns.net. [TTL=1800]IP=66.196.118.35 [TTL=300]
IP=98.136.216.26 [TTL=300]
IP=66.196.118.37 [TTL=300]
IP=63.250.192.45 [TTL=300]
IP=63.250.192.46 [TTL=300]
IP=98.136.217.203 [TTL=300]
IP=98.136.216.25 [TTL=300]
IP=98.138.112.38 [TTL=300]
10mta6.am0.yahoodns.net. [TTL=1800]IP=98.136.217.203 [TTL=300]
IP=66.196.118.36 [TTL=300]
IP=98.138.112.35 [TTL=300]
IP=63.250.192.45 [TTL=300]
IP=66.196.118.37 [TTL=300]
IP=98.136.217.202 [TTL=300]
IP=66.196.118.33 [TTL=300]
IP=63.250.192.46 [TTL=300]
PASSInvalid charactersOK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASSAll MX IPs publicOK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASSMX records are not CNAMEsOK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASSMX is host name, not IPOK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
PASSMultiple MX recordsOK. You have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you.
PASSDiffering MX-A recordsOK. I did not detect differing IPs for your MX records. This would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records.
FAILEDDuplicate MX recordsFAILED. -17 duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
FAILEDReverse DNS entries for MX recordsFAILED. The IPs of not all of your mail server(s) have correct reverse DNS (PTR) entries. The reverse DNS entries are:

26.216.136.98.in-addr.arpa.mta-v1.mail.vip.gq1.yahoo.com.[TTL=1800]
37.112.138.98.in-addr.arpa.mta-v5.mail.vip.ne1.yahoo.com.[TTL=1800]
36.118.196.66.in-addr.arpa.mta-v3.mail.vip.bf1.yahoo.com.[TTL=1800]
33.112.138.98.in-addr.arpa.mta-v2.mail.vip.ne1.yahoo.com.[TTL=1800]
32.112.138.98.in-addr.arpa.mta-v6.mail.vip.ne1.yahoo.com.[TTL=1800]
34.112.138.98.in-addr.arpa.mta-v3.mail.vip.ne1.yahoo.com.[TTL=1800]
202.217.136.98.in-addr.arpa.mta-v3.mail.vip.gq1.yahoo.com.[TTL=1800]
240.118.196.66.in-addr.arpa.mta-v6.mail.vip.bf1.yahoo.com.[TTL=1800]
35.118.196.66.in-addr.arpa.mta-v4.mail.vip.bf1.yahoo.com.[TTL=1800]
26.216.136.98.in-addr.arpa.mta-v1.mail.vip.gq1.yahoo.com.[TTL=1800]
37.118.196.66.in-addr.arpa.mta-v5.mail.vip.bf1.yahoo.com.[TTL=1800]
45.192.250.63.in-addr.arpa.mta-v5.mail.vip.gq1.yahoo.com.[TTL=1800]
46.192.250.63.in-addr.arpa.mta-v6.mail.vip.gq1.yahoo.com.[TTL=1800]
203.217.136.98.in-addr.arpa.mta-v4.mail.vip.gq1.yahoo.com.[TTL=1800]
25.216.136.98.in-addr.arpa.mta-v2.mail.vip.gq1.yahoo.com.[TTL=1800]
38.112.138.98.in-addr.arpa.mta-v1.mail.vip.ne1.yahoo.com.[TTL=1800]
203.217.136.98.in-addr.arpa.mta-v4.mail.vip.gq1.yahoo.com.[TTL=1800]
36.118.196.66.in-addr.arpa.mta-v3.mail.vip.bf1.yahoo.com.[TTL=1800]
35.112.138.98.in-addr.arpa.mta-v4.mail.vip.ne1.yahoo.com.[TTL=1800]
45.192.250.63.in-addr.arpa.mta-v5.mail.vip.gq1.yahoo.com.[TTL=1800]
37.118.196.66.in-addr.arpa.mta-v5.mail.vip.bf1.yahoo.com.[TTL=1800]
202.217.136.98.in-addr.arpa.mta-v3.mail.vip.gq1.yahoo.com.[TTL=1800]
33.118.196.66.in-addr.arpa.mta-v1.mail.vip.bf1.yahoo.com.[TTL=1800]
46.192.250.63.in-addr.arpa.mta-v6.mail.vip.gq1.yahoo.com.[TTL=1800]
MailPASSConnect to mail serversOK. You were able to connect to all of your mailservers.
FAILEDMail server host name in greetingFAILED. Not all of your mailservers have their host name in the greeting:

mta7.am0.yahoodns.net <> mta1284.mail.bf1.yahoo.com
mta5.am0.yahoodns.net <> mta1000.mail.bf1.yahoo.com
mta6.am0.yahoodns.net <> mta1226.mail.bf1.yahoo.com
INFOSending test mailIt is temporary disabled
PASSOpen relay testOK. All of your mailservers appear to be closed to relaying.

mta7.am0.yahoodns.net.: 553 5.7.1 [BL21] Connections will not be accepted from 77.222.132.21, because the ip is in Spamhaus's list; see http://postmaster.yahoo.com/550-bl23.html
mta5.am0.yahoodns.net.: 553 5.7.1 [BL21] Connections will not be accepted from 77.222.132.21, because the ip is in Spamhaus's list; see http://postmaster.yahoo.com/550-bl23.html
mta6.am0.yahoodns.net.: 553 5.7.1 [BL21] Connections will not be accepted from 77.222.132.21, because the ip is in Spamhaus's list; see http://postmaster.yahoo.com/550-bl23.html
FAILEDSPF recordFAILED. You don't seem to have an SPF record. This is not very good, as the SPF record helps to prevent spammers from abusing your domain.
WWWINFOWWW RecordYour www.ymail.com. A record is:

www.ymail.com. CNAME rc.yahoo.com. [TTL=7200]
rc.yahoo.com. CNAME rc.g01.yahoodns.net. [TTL=300]
rc.g01.yahoodns.net. CNAME any-rc.a01.yahoodns.net. [TTL=300]
any-rc.a01.yahoodns.net. A 77.238.178.122 [TTL=300]
any-rc.a01.yahoodns.net. A 87.248.120.148 [TTL=300]
PASSAll WWW IPs publicOK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
FAILEDCNAME LookupFAILED. Your web site (www.ymail.com.) has a CNAME record.
INFODomain A LookupYour ymail.com. A record is:

ymail.com. A 68.180.206.184 [TTL=7200]
ymail.com. A 98.139.102.145 [TTL=7200]
PASSConnect to HTTP serversOK. You were able to connect to all of your HTTP servers.

www.ymail.com. [77.238.178.122]: HTTP/1.1 301 Moved Permanently Date: Sun, 20 Apr 2014 15:51:27 GMT P3P: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"

www.ymail.com. [87.248.120.148]: HTTP/1.1 301 Moved Permanently Date: Sun, 20 Apr 2014 15:51:27 GMT P3P: policyref="http://info.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC GOV"