Report for springfieldcityclerk.com

Report created on: Fri, 25 Apr 2025 19:48:15 GMT
Parent
100
NS
3
SOA
0
MX
100
Mail
100
Web
75
Parent
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (b.gtld-servers.net.).
Domain NS records:
  • cwlpns1.cwlp.com. TTL=172800 [64.107.110.200] [NO GLUE6]
  • cwlpns2.cwlp.com. TTL=172800 [64.107.110.199] [NO GLUE6]
Name Servers Have A Records
OK. Found A records for all name servers.
  • cwlpns1.cwlp.com. → 64.107.110.200
  • cwlpns2.cwlp.com. → 64.107.110.199
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.
  • cwlpns1.cwlp.com. → ?
  • cwlpns2.cwlp.com. → ?
To reach your name servers via IPv6 an AAAA record is needed for each name server.
NS
NS Records
Your name servers returned 1 NS records:
  • mcwdmzwb03. TTL=3600 [10.1.96.102] [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
WARNING: The following name servers announces themselves as open DNS servers:
  • udp4:64.107.110.199
  • udp4:64.107.110.200
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
WARNING: Domain has 1 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
FAIL: We found different NS records on your name servers:
  • udp4:64.107.110.199: [mcwdmzwb03.]
  • udp4:64.107.110.200: [mcwdmzwb02.]
Each name server should return identical NS records.
Check for Lame Name servers
WARNING: We found name servers which are not authoritative for your domain. Lame name servers:
  • udp4:64.107.110.199
  • udp4:64.107.110.200
All of your name server should be configured either as master or slave for your domain, if a NS records points to a name server that does not answer authoritatively, name server is called lame name server.
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
FAIL: We found name servers without A records.
  • mcwdmzwb03. → ?
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
NOTICE: We found name servers without AAAA records.
  • mcwdmzwb03. → ?
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
WARNING: Found stealth name servers:
  • mcwdmzwb03.
All name servers returned by domain name servers should be listed at parent servers.
Check for Missing Name Servers
WARNING: Found missing name servers:
  • cwlpns1.cwlp.com.
  • cwlpns2.cwlp.com.
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
WARNING: Couldn't connect using TCP protocol:
  • tcp4:64.107.110.199
  • tcp4:64.107.110.200
Check your name server's configurations and firewall rules. 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 0 different C class networks:
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:
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
Mail
Web
Resolve Domain Name
WARNING: Could not resolve domain springfieldcityclerk.com..
Resolve WWW
WARNING: Could not resolve domain www.springfieldcityclerk.com..

Report completed in 2.24 seconds.

Recent reports: eyz.swiss arin.net byes.live 6sense.com.au mehrgasht.com