DNS Report for telecentro.com.ar
|Report created on: Wed, 24 Sep 2014 15:54:10 GMT||||
|NS Records at Parent Servers||info||
We have successfully fetched domain's NS records from parent name server (athea.ar.).
Domain NS records:
|Missing Glue||pass||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 (athea.ar.).|
|Name Servers Have A Records||pass||OK.
Found A records for all name servers.
|Name Servers Have AAAA Records||notice||NOTICE:
While reading domain NS records at parent name servers,
we found name servers without AAAA records.
Your name servers returned 2 NS records:
|All Name Servers Responded||pass||OK. All your name servers responded. We queried domain's records from all of your name servers and we received them successfully.|
|Glue Check||pass||OK. No differences found. The glue provided by the parent name servers has to match the data provided by the authoritative name servers.|
|Allow Recursive Queries||pass||OK. Domain name servers are not allowing recursive queries. On all name servers which acts as caching name servers recursive queries should be restricted to local networks. Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks. Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic, email and other traffic to malicious hosts compromising security.|
|Check Name Servers Count||pass||OK. Domain has 2 name servers. Recommended number, between 2 and 7 name servers (RFC 2182 recommends to have at least 3 authoritative name servers for domains).|
|Identical NS Records||pass||OK. All your name servers reported identical NS records. Each name server should return identical NS records.|
|Check for Lame Name servers||pass||OK. No lame name servers found. All of your name servers are configured to be either master or slave for your domain.|
|Check All IPs are Public||pass||OK. No private IPs found. Name servers using private IPs can't be reached from the Internet causing DNS delays.|
|Name Servers Have A Records||pass||OK.
Found A records for each name servers.
|Name Servers Have AAAA Records||notice||NOTICE:
We found name servers without AAAA records.
|Name Servers Have Valid Names||pass||OK. All names are valid. Name server name should be a valid host name, no partial name or IP address.|
|Check for Stealth Name Servers||pass||OK. No stealth name servers found. All name servers returned by domain name servers should be listed at parent servers.|
|Check for Missing Name Servers||pass||OK. No missing name servers found. All name servers returned by the parent name servers should have an NS record at your name servers.|
|No CNAME in NS Records||pass||OK. No CNAMEs found in NS 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.|
|Allow TCP connections||pass||OK. All name servers are allowing TCP connections. When response to a DNS query exceeds 512 bytes, TCP is negotiated and used, all name servers should allow TCP connections (port 53).|
|Name Servers Distributed on Multiple Networks||warn||WARNING:
All name servers are located in one C class network:
|Name Servers Distributed on Multiple ASNs||warn||WARNING:
All name servers are located in one Autonomous System:
|Name Servers Versions||pass||OK.
Name servers software versions are not exposed:
|Check SOA Record||info||
Domain SOA Record:
|Name Servers Agreement on Serial Number||pass||OK. All name servers (2) have the same serial number . Having different serials on your name servers may show inconsistencies between name servers configuration (multiple masters), or communication errors (ACL and firewall issues).|
|SOA Number Format||pass||OK. Serial number format OK . 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.|
|SOA Mname||pass||OK. Primary name server is ns1.telecentro.com.ar. 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.|
|SOA Rname||pass||OK. Contact email for DNS problems is email@example.com. (webmaster.telecentro.com.ar.). 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.|
|SOA Refresh||pass||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.|
|SOA Retry||pass||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.|
|SOA Expire||warn||WARNING: Expire interval is 3600000. 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.|
|SOA Minimum TTL||pass||OK. Minimum TTL value is 86400. Recommended values [3600 .. 86400] (1 hour ... 1 day). Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves to cache negative responses.|
Your name servers returned 1 MX records:
|Identical MX Records||pass||OK. All name servers returned identical MX records.|
|Mail Servers Have A Records||pass||OK.
Found A records for all mail servers.
|Mail Servers Have AAAA Records||notice||NOTICE:
While reading domain NS records at parent mail servers,
we found mail servers without AAAA records.
|Reverse Entries for MX records||pass||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||pass||OK. No invalid characters found. Name field from MX records should be a valid host name.|
|Check MX Records IPs are Public||pass||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||pass||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||pass||OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.|
|No CNAME in MX Records||pass||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||pass||OK. Mail servers IPs are not blacklisted.|
|Check Google Apps Settings||skip||Test ignored, domain is not using Google Apps.|
|Connect to Mail Servers||pass||OK.
Successfully connected to all mail servers.
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):
|Accepts Postmaster Address||pass||OK.
All mail servers are accepting emails to
|Accepts Abuse Address||skip||
Temporary error, could not determine if
all mail servers are accepting emails to
|Check SPF record||pass||OK.
Found SPF record:
v=spf1 a mx ~all or v=spf1 a mx include:_spf.google.com ~all if you are using Google Apps.
|Identical TXT records||pass||OK. Name servers returned identical TXT records. Only SPF records are compared, all name servers should return identical SPF records.|
|Identical SPF records||skip||No SPF type records found. All name servers should return identical SPF records.|
|Check DMARC record||notice||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.|
|Resolve Domain Name||pass||OK.
Domain telecentro.com.ar. resolves to:
|Domain Name IPs are Public||pass||OK. No private IPs found for telecentro.com.ar.. Web servers using private IPs can't be reached from the Internet.|
Domain www.telecentro.com.ar. resolves to:
|WWW IPs are Public||pass||OK. No private IPs found for www.telecentro.com.ar.. Web servers using private IPs can't be reached from the Internet.|
Report completed in 31.99 seconds.