Report for fthcapital.com

OK. Found A records for all name servers.

• ns1.dnsowl.com. → 162.159.27.173, 162.159.26.136
• ns2.dnsowl.com. → 162.159.26.49, 162.159.27.130
• ns3.dnsowl.com. → 162.159.27.98, 162.159.26.234

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

OK. Found AAAA records for all name servers.

• ns1.dnsowl.com. → 2400:cb00:2049:1::a29f:1bad, 2400:cb00:2049:1::a29f:1a88
• ns2.dnsowl.com. → 2400:cb00:2049:1::a29f:1b82, 2400:cb00:2049:1::a29f:1a31
• ns3.dnsowl.com. → 2400:cb00:2049:1::a29f:1aea, 2400:cb00:2049:1::a29f:1b62

To reach your name servers via IPv6 an AAAA record is needed for each name server.

OK. All name servers returned identical MX records.

OK. Found A records for all mail servers.

• in.mail.tm. → 49.12.18.190

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

OK. Found AAAA records for all mail servers.

• in.mail.tm. → 2a01:4f8:c011:4d4::1

To reach your mail servers via IPv6 an AAAA 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 fthcapital.com. resolves to:

• 51.254.35.55

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

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

• 51.254.35.55

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