Report for diagenicsgroup.com

OK. Parent name servers are offering glue for domain's name servers. We received name servers list and it's IP addresses from parent name server (m.gtld-servers.net.).

OK. Found A records for all name servers.

• ns1.diagenicsgroup.com. → 45.84.221.235
• ns2.diagenicsgroup.com. → 45.84.221.235

To reach your name servers via IPv4 an A record is needed for each name server.

OK. All name servers (2) have the same serial number [2024051601]. Having different serials on your name servers may show inconsistencies between name servers configuration (multiple masters), or communication errors (ACL and firewall issues).

OK. Serial number format OK [2024051601]. Your serial number is following general convention for serial number 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.

OK. Primary name server is ns1.diagenicsgroup.com. and is listed 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.

OK. Contact email for DNS problems is [email protected]. (admin.diagenicsgroup.com.). 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.

OK. Refresh interval is 7200. Recommended values [1200 .. 43200] (20 min ... 12 hours). Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.

OK. Retry interval is 3600. 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.

OK. Expire interval is 1209600. 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.

OK. All name servers returned identical MX records.

OK. Found A records for all mail servers.

• smtp.ldap.com.tr. → 185.81.237.137

To reach your mail servers via IPv4 an A record is needed for each mail server.

OK. All mail servers have reverse DNS entries configured correctly.

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.

OK. No invalid characters found. Name field from MX records should be a valid host name.

OK. No private IPs found. Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.

OK. No MX records duplicates (same IP addresses) found. Although technically valid, duplicate MX records have no benefits and can cause confusion.

OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.

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.

OK. Mail servers IPs are not blacklisted.

OK. Domain diagenicsgroup.com. resolves to:

• 45.84.221.235

OK. No private IPs found for diagenicsgroup.com.. Web servers using private IPs can't be reached from the Internet.

OK. Domain www.diagenicsgroup.com. resolves to:

• 45.84.221.235

OK. No private IPs found for www.diagenicsgroup.com.. Web servers using private IPs can't be reached from the Internet.