Report for nanddosalas.com

Report created on: Thu, 25 Nov 2021 23:58:24 GMT
Parent
100
NS
100
SOA
0
MX
95
Mail
81
Web
87
Parent
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (h.gtld-servers.net.).
Domain NS records:
  • dns1.registrar-servers.com. TTL=172800 [156.154.132.200] [2610:a1:1024::200]
  • dns2.registrar-servers.com. TTL=172800 [156.154.133.200] [2610:a1:1025::200]
Name Servers Have A Records
OK. Found A records for all name servers.
  • United States dns1.registrar-servers.com. → 156.154.132.200
  • United States dns2.registrar-servers.com. → 156.154.133.200
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.
  • dns1.registrar-servers.com. → 2610:a1:1024::200
  • dns2.registrar-servers.com. → 2610:a1:1025::200
To reach your name servers via IPv6 an AAAA record is needed for each name server.
NS
NS Records
Your name servers returned 2 NS records:
  • dns1.registrar-servers.com. TTL=1800 [NO GLUE4] [NO GLUE6]
  • dns2.registrar-servers.com. TTL=1800 [NO GLUE4] [NO GLUE6]
All Name Servers Responded
OK. All your name servers responded. We queried domain's records from all of your name servers and we received them successfully.
Glue Check
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
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
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
OK. All your name servers reported identical NS records. Each name server should return identical NS records.
Check for Lame Name servers
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
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
OK. Found A records for each name servers.
  • United States dns1.registrar-servers.com. → 156.154.132.200
  • United States dns2.registrar-servers.com. → 156.154.133.200
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.
  • dns1.registrar-servers.com. → 2610:a1:1024::200
  • dns2.registrar-servers.com. → 2610:a1:1025::200
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Name Servers Have Valid Names
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
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
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
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
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
OK. Name servers are dispersed on 2 different C class networks:
  • 156.154.132.0/24:
    • dns1.registrar-servers.com.
  • 156.154.133.0/24:
    • dns2.registrar-servers.com.
Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Distributed on Multiple ASNs
OK. Name servers are dispersed on 12 different Autonomous Systems:
  • AS397213:
    • dns1.registrar-servers.com.
  • AS397215:
    • dns2.registrar-servers.com.
  • AS397218:
    • dns1.registrar-servers.com.
  • AS397220:
    • dns2.registrar-servers.com.
  • AS397224:
    • dns2.registrar-servers.com.
  • AS397228:
    • dns1.registrar-servers.com.
  • AS397231:
    • dns1.registrar-servers.com.
    • dns2.registrar-servers.com.
  • AS397232:
    • dns1.registrar-servers.com.
  • AS397233:
    • dns2.registrar-servers.com.
  • AS397235:
    • dns1.registrar-servers.com.
  • AS397238:
    • dns1.registrar-servers.com.
    • dns2.registrar-servers.com.
  • AS397242:
    • dns1.registrar-servers.com.
Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Versions
OK. Name servers software versions are not exposed:
  • 156.154.132.200: "UltraDNS Resolver"
  • 156.154.133.200: "UltraDNS Resolver"
  • 2610:a1:1024::200: "UltraDNS Resolver"
  • 2610:a1:1025::200: "UltraDNS Resolver"
Exposing name server's versions may be risky, when a new vulnerability is found your name servers may be automatically exploited by script kiddies until you patch the system. Learn how to hide version.
SOA
MX
MX Records
Your name servers returned 5 MX records:
  • 10 eforward1.registrar-servers.com. TTL=1800
  • 10 eforward2.registrar-servers.com. TTL=1800
  • 10 eforward3.registrar-servers.com. TTL=1800
  • 15 eforward4.registrar-servers.com. TTL=1800
  • 20 eforward5.registrar-servers.com. TTL=1800
Identical MX Records
OK. All name servers returned identical MX records.
Mail Servers Have A Records
OK. Found A records for all mail servers.
  • United States eforward1.registrar-servers.com. → 162.255.118.51
  • United States eforward2.registrar-servers.com. → 162.255.118.52
  • United States eforward3.registrar-servers.com. → 162.255.118.51
  • United States eforward4.registrar-servers.com. → 162.255.118.52
  • United States eforward5.registrar-servers.com. → 162.255.118.51
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.
  • eforward1.registrar-servers.com. → ?
  • eforward2.registrar-servers.com. → ?
  • eforward3.registrar-servers.com. → ?
  • eforward4.registrar-servers.com. → ?
  • eforward5.registrar-servers.com. → ?
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
eforward1.registrar-servers.com. 162.255.118.51 eforward1.registrar-servers.com. 162.255.118.51
eforward1.registrar-servers.com. 162.255.118.51 eforward3.registrar-servers.com. 162.255.118.51
eforward2.registrar-servers.com. 162.255.118.52 eforward2.registrar-servers.com. 162.255.118.52
eforward3.registrar-servers.com. 162.255.118.51 eforward1.registrar-servers.com. 162.255.118.51
eforward3.registrar-servers.com. 162.255.118.51 eforward3.registrar-servers.com. 162.255.118.51
eforward4.registrar-servers.com. 162.255.118.52 eforward2.registrar-servers.com. 162.255.118.52
eforward5.registrar-servers.com. 162.255.118.51 eforward1.registrar-servers.com. 162.255.118.51
eforward5.registrar-servers.com. 162.255.118.51 eforward3.registrar-servers.com. 162.255.118.51

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
WARNING: MX records duplicates (same IP address):
  • 162.255.118.51: [eforward1.registrar-servers.com. eforward3.registrar-servers.com. eforward5.registrar-servers.com.]
  • 162.255.118.52: [eforward2.registrar-servers.com. eforward4.registrar-servers.com.]
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.
  • eforward1.registrar-servers.com.:
    220 asp-relay.et.namecheap.tech ESMTP Postfix
  • eforward2.registrar-servers.com.:
    220 asp-relay.et.namecheap.tech ESMTP Postfix
  • eforward3.registrar-servers.com.:
    220 asp-relay.et.namecheap.tech ESMTP Postfix
  • eforward4.registrar-servers.com.:
    220 asp-relay.et.namecheap.tech ESMTP Postfix
  • eforward5.registrar-servers.com.:
    220 asp-relay.et.namecheap.tech ESMTP Postfix
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):
  • eforward1.registrar-servers.com.asp-relay.et.namecheap.tech
  • eforward2.registrar-servers.com.asp-relay.et.namecheap.tech
  • eforward3.registrar-servers.com.asp-relay.et.namecheap.tech
  • eforward4.registrar-servers.com.asp-relay.et.namecheap.tech
  • eforward5.registrar-servers.com.asp-relay.et.namecheap.tech
Accepts Postmaster Address
WARNING: Found mail servers which are not 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
WARNING: Found mail servers which are not 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.
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 nanddosalas.com. resolves to:
  • United States 172.217.14.110
Domain Name IPs are Public
OK. No private IPs found for nanddosalas.com.. Web servers using private IPs can't be reached from the Internet.
Resolve WWW
WARNING: Could not resolve domain www.nanddosalas.com..

Report completed in 0.32 seconds.

Recent reports: bluebyte.gr bluebyte.gr bluebyte.gr ugyz5b2me3lede7uk5fvlzsfnabqeaqbaeaq.a.e.e5.sk bluebyte.gr