Report for

Report created on: Wed, 16 Sep 2020 10:03:39 GMT
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (
Domain NS records:
  • TTL=172800 [,] [NO GLUE6]
  • TTL=172800 [] [NO GLUE6]
  • TTL=172800 [] [2408:400a:32:9000:4240:dd70:6a99:f5e8]
  • TTL=172800 [] [240e:980:8500::79cc:a38e]
Name Servers Have A Records
OK. Found A records for all name servers.
  • China →
  • China →
  • China →
  • China →
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
OK. Found AAAA records for all name servers.
  • → 2001:470:c:8c9::2
  • → 2001:19f0:7001:3c93:5400:2ff:fe79:5c33
  • → 240e:980:8500::79cc:a38e
  • → 2408:400a:32:9000:4240:dd70:6a99:f5e8
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Check SOA Record
Domain SOA Record:
  • Primary nameserver: .
  • Hostmaster (e-mail): hostmaster.nameserver.
  • Serial: 28
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 5
Name Servers Agreement on Serial Number
WARNING: We found different serial numbers on your name servers, it's OK if you had modified your zone recently.
  • 28
  • 2001:19f0:7001:3c93:5400:2ff:fe79:5c33: 28
  • 2001:470:c:8c9::2: 0
  • 28
  • 2408:400a:32:9000:4240:dd70:6a99:f5e8: 28
  • 240e:980:8500::79cc:a38e: 28
Having different serials on your name servers may show inconsistencies between name servers configuration (multiple masters), or communication errors (ACL and firewall issues).
SOA Number Format
NOTICE: Although your serial is valid [28], it's not using recommended serial number format YYYYMMDDnn, where YYYY is four-digit year number, MM is the month, DD is the day and nn is the sequence number in case zone file is updated more than once per day.
SOA Mname
WARNING: Primary name server . listed in SOA Record is not found at the parent name servers. The MNAME field defines the Primary Master name server for the zone, this name server should be found in your NS records.
SOA Rname
OK. Contact email for DNS problems is hostmaster@nameserver. (hostmaster.nameserver.). RNAME field defines an administrative email for your zone. RFC2142 recommends using hostmaster e-mail for this purpose, but any valid e-mail address can be used.
SOA Refresh
OK. Refresh interval is 28800. Recommended values [1200 .. 43200] (20 min ... 12 hours). Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.
SOA Retry
OK. Retry interval is 7200. Recommended values [120 .. 7200] (2 minutes .. 2 hours). Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.
SOA Expire
OK. Expire interval is 604800. Recommended values [604800 .. 1209600] (1 week ... 2 weeks). Expiry defines zone expiration time in seconds after which slave must re-validate zone file, if contacting master fails then slave will stop responding to any queries.
SOA Minimum TTL
WARNING: Minimum TTL value is 5. Recommended values [3600 .. 86400] (1 hour ... 1 day). Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves to cache negative responses.
MX Records
Your name servers returned 1 MX records. Your MX records sorted by priority (lower numbers have higher priority):
  • 10 TTL=3600
Identical MX Records
OK. All name servers returned identical MX records.
Mail Servers Have A Records
OK. Found A records for all mail servers.
  • China →
To reach your mail servers via IPv4 an A record is needed for each mail server.
Mail Servers Have AAAA Records
NOTICE: While reading domain NS records at parent mail servers, we found mail servers without AAAA records.
  • → ?
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records
WARNING: Found mail servers with inconsistent reverse DNS entries. You should fix them if you are using those servers to send email.
Server IP PTR (Reverse) IPs ? ?

All mail servers should have a reverse DNS (PTR) entry for each IP address (RFC 1912). Missing reverse DNS entries will make many mail servers to reject your e-mails or mark them as SPAM.

All IP's reverse DNS entries should resolve back to IP address (IP → PTR → IP). Many mail servers are configured to reject e-mails from IPs with inconsistent reverse DNS configuration.

Check MX Records for Invalid Chars
OK. No invalid characters found. Name field from MX records should be a valid host name.
Check MX Records IPs are Public
OK. No private IPs found. Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.
Check MX Records for Duplicates
OK. No MX records duplicates (same IP addresses) found. Although technically valid, duplicate MX records have no benefits and can cause confusion.
Only Host Names in MX Records
OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.
No CNAME in MX Records
OK. No CNAMEs found in MX records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA) and must not point to any CNAME records. RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record) it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with NS and MX records. Despite this restrictions, there are many working configuration using CNAME with NS and MX records.
RBL Check
OK. Mail servers IPs are not blacklisted.
Connect to Mail Servers
OK. Successfully connected to all mail servers.
    220 TurboMail SMTP Service ready
To receive emails, mail servers should allow TCP connections on port 25.
Mail Greeting
NOTICE: I've found differences between mail server host names and greeting host name. The following mail servers claims to be other hosts (reverse DNS checks may be wrong):
Accepts Postmaster Address
WARNING: Found mail servers which are not accepting emails to address:
    >> MAIL FROM: <>
    << 250 OK
    >> RCPT TO: <>
    << 550 The email account that you tried to reach does not exist. Please try(174965DD571)
RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster. To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.
Accepts Abuse Address
WARNING: Found mail servers which are not accepting emails to address:
    >> MAIL FROM: <>
    << 250 OK
    >> RCPT TO: <>
    << 550 The email account that you tried to reach does not exist. Please try(174965DD571)
Check SPF record
WARNING: Domain doesn't have SPF record. SPF (Sender Policy Framework) record is designed to prevent e-mail spoofing. Typical SPF record would be:
v=spf1 a mx ~all or v=spf1 a mx ~all if you are using Google Apps.
Check DMARC record
NOTICE: Domain doesn't have DMARC record. DMARC (Domain-based Message Authentication, Reporting & Conformance) helps reducing potential of email-based abuse such as spam and phishing e-mails.
Resolve Domain Name
WARNING: Could not resolve domain
Resolve WWW
WARNING: Could not resolve domain

Report completed in 11.53 seconds.

Recent reports: