Report for mpcfg.co.cu
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (
ns2.etecsa.net.).
Domain NS records:
-
servermp.mpcfg.co.cu. TTL=2000
[200.55.146.66]
[NO GLUE6]
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 (ns2.etecsa.net.).
Name Servers Have A Records
OK.
Found A records for all name servers.
- servermp.mpcfg.co.cu. → 200.55.146.66
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.
- servermp.mpcfg.co.cu. → ?
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Could not get NS records from your name servers.
Could not get SOA record from your name servers.
Your name servers returned
1 MX records:
-
20 servermp.mpcfg.co.cu. TTL=38400
OK.
All name servers returned identical MX records.
Mail Servers Have A Records
OK.
Found A records for all mail servers.
- servermp.mpcfg.co.cu. → 200.55.146.66
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.
- servermp.mpcfg.co.cu. → ?
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.
|
Server |
IP |
PTR (Reverse) |
IPs |
|
servermp.mpcfg.co.cu. |
200.55.146.66 |
servermp.mpcfg.co.cu. |
200.55.146.66 |
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.
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.
Check Google Apps Settings
Test ignored, domain is not using Google Apps.
OK.
Successfully connected to all mail servers.
To receive emails, mail servers should allow TCP connections on port 25.
OK.
No differences between mail server host names and greeting host name.
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.
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.
No TXT records found.
Only SPF records are compared, all name servers should return identical SPF records.
No SPF type records found.
All name servers should return identical SPF records.
OK.
Found DMARC record:
- v=DMARC1; p=none; rua=mailto:[email protected]; fo=0; adkim=r; aspf=r; rf=afrf; sp=none;
DMARC
(Domain-based Message Authentication, Reporting & Conformance)
helps reducing potential of email-based abuse such as spam and
phishing e-mails.
OK.
Domain
mpcfg.co.cu. resolves to:
Domain Name IPs are Public
OK.
No private IPs found for mpcfg.co.cu..
Web servers using private IPs can't be reached from the Internet.
OK.
Domain
www.mpcfg.co.cu. resolves to:
OK.
No private IPs found for www.mpcfg.co.cu..
Web servers using private IPs can't be reached from the Internet.
Report completed in 30.33 seconds.
Recent reports:
kotaksecurities.com
kotak811.com
811.com
huawei.com
huawei.com