Report for spdm.org.br

Report created on: Wed, 15 Jan 2025 11:33:41 GMT
Parent
100
NS
0
SOA
0
MX
60
Mail
100
Web
20
Parent
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (d.dns.br.).
Domain NS records:
  • pns21.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
  • pns22.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
  • pns23.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
  • pns24.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
Name Servers Have A Records
OK. Found A records for all name servers.
  • pns21.cloudns.net. → 185.136.96.96
  • pns22.cloudns.net. → 185.136.97.96
  • pns23.cloudns.net. → 185.136.98.96
  • pns24.cloudns.net. → 185.136.99.96
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.
  • pns21.cloudns.net. → 2a06:fb00:1::1:96
  • pns22.cloudns.net. → 2a06:fb00:1::2:96
  • pns23.cloudns.net. → 2a06:fb00:1::3:96
  • pns24.cloudns.net. → 2a06:fb00:1::4:96
To reach your name servers via IPv6 an AAAA record is needed for each name server.
NS
SOA
MX
MX Records
Your name servers returned 1 MX records:
  • 0 localhost. TTL=120
Identical MX Records
OK. All name servers returned identical MX records.
Mail Servers Have A Records
FAIL: I've found mail servers without A records:
  • localhost. → ?
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.
  • localhost. → ?
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records
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.

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.
Mail
Web
Resolve Domain Name
OK. Domain spdm.org.br. resolves to:
  • 127.0.0.1
Domain Name IPs are Public
FAIL: Found private IPs:
  • spdm.org.br.: [127.0.0.1 ::1]
Web servers using private IPs can't be reached from the Internet.
Resolve WWW
OK. Domain www.spdm.org.br. resolves to:
  • 127.0.0.1
WWW IPs are Public
FAIL: Found private IPs:
  • www.spdm.org.br.: [127.0.0.1 ::1]
Web servers using private IPs can't be reached from the Internet.

Report completed in 0.04 seconds.

Recent reports: exportfame.com.br forbak.eu cathedral-networks.org gmztv.com prreqcroab.icu