Report for manchesterchamber.net

Report created on: Tue, 14 Feb 2017 21:19:05 GMT
Parent
100
NS
0
SOA
0
MX
95
Mail
93
Web
100
Parent
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (d.gtld-servers.net.).
Domain NS records:
  • ns1.pendingrenewaldeletion.com. TTL=172800 [207.204.40.151] [NO GLUE6]
  • ns2.pendingrenewaldeletion.com. TTL=172800 [207.204.21.151] [NO GLUE6]
Name Servers Have A Records
OK. Found A records for all name servers.
  • ns1.pendingrenewaldeletion.com. → 207.204.40.151
  • ns2.pendingrenewaldeletion.com. → 207.204.21.151
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
NOTICE: While reading domain NS records at parent name servers, we found name servers without AAAA records.
  • ns1.pendingrenewaldeletion.com. → ?
  • ns2.pendingrenewaldeletion.com. → ?
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:
  • 5 mail.b-io.co. 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.
  • mail.b-io.co. → 198.133.159.126, 198.133.159.133, 198.133.159.132, 198.133.159.125, 198.133.159.120, 198.133.159.136, 198.133.159.121, 198.133.159.138, 198.133.159.124, 198.133.159.134, 198.133.159.119, 198.133.159.137, 198.133.159.123, 198.133.159.122, 198.133.159.139, 198.133.159.135
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.
  • mail.b-io.co. → ?
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
mail.b-io.co. 198.133.159.126 ? ?
mail.b-io.co. 198.133.159.133 ? ?
mail.b-io.co. 198.133.159.132 ? ?
mail.b-io.co. 198.133.159.125 ? ?
mail.b-io.co. 198.133.159.120 ? ?
mail.b-io.co. 198.133.159.136 ? ?
mail.b-io.co. 198.133.159.121 ? ?
mail.b-io.co. 198.133.159.138 ? ?
mail.b-io.co. 198.133.159.124 ? ?
mail.b-io.co. 198.133.159.134 ? ?
mail.b-io.co. 198.133.159.119 ? ?
mail.b-io.co. 198.133.159.137 ? ?
mail.b-io.co. 198.133.159.123 ? ?
mail.b-io.co. 198.133.159.122 ? ?
mail.b-io.co. 198.133.159.139 ? ?
mail.b-io.co. 198.133.159.135 ? ?

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
Connect to Mail Servers
OK. Successfully connected to all mail servers.
  • mail.b-io.co.: 
    220 SMMail 1.48.1 ESMTP
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):
  • mail.b-io.co. → smmail
Accepts Postmaster Address
OK. All mail servers are accepting emails to [email protected] address: 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
OK. All mail servers are accepting emails to [email protected] address:
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 include:_spf.google.com ~all if you are using Google Apps.
Identical TXT records
OK. Name servers returned identical TXT records. Only SPF records are compared, all name servers should return identical SPF records.
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.
Web
Resolve Domain Name
OK. Domain manchesterchamber.net. resolves to:
  • 208.91.197.132
Domain Name IPs are Public
OK. No private IPs found for manchesterchamber.net.. Web servers using private IPs can't be reached from the Internet.
Resolve WWW
OK. Domain www.manchesterchamber.net. resolves to:
  • 208.91.197.132
WWW IPs are Public
OK. No private IPs found for www.manchesterchamber.net.. Web servers using private IPs can't be reached from the Internet.

Report completed in 4.34 seconds.

Recent reports: engen.mu comclub.gr comclub.gr free-apps-android.com revenuepassif.fr