webcom.com

Checked 22 October 2026, 11:24 UTC · via 8.8.8.8
✗Problems found
21 passed 4 warnings 2 failed 4 info

Registration

info

.com generic · Register.com - Network Solutions, LLC · expires 2030-07-28

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Register.com - Network Solutions, LLC
Registered
29 July 1994
Last changed
6 August 2026
Expires
28 July 2030
Status
client transfer prohibited
Registry nameservers
dns1.registeredsite.com, dns2.registeredsite.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2030-07-28 #3
    The registration is valid until 2030-07-28 (1374 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns1.registeredsite.com, dns2.registeredsite.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.registeredsite.com, dns2.registeredsite.com
NS in the zone
dns2.registeredsite.com, dns3.registeredsite.com
NameserverAddressesNetwork (AS)Glue
dns1.registeredsite.com (parent only)162.214.41.47AS46606 UNIFIEDLAYER-AS-1 - Unified Layer, US162.214.41.47
dns2.registeredsite.com207.204.21.31AS19871 NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US207.204.21.31
dns3.registeredsite.com (zone only)207.204.21.31AS19871 NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.registeredsite.com, dns2.registeredsite.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.registeredsite.com; only in the zone: dns3.registeredsite.com. dns2.registeredsite.com, dns3.registeredsite.com report NS dns2.registeredsite.com dns3.registeredsite.com.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS19871 (NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US): 2 addresses; AS46606 (UNIFIEDLAYER-AS-1 - Unified Layer, US): 1 address.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.registeredsite.com 162.214.41.47no responsenono / no--
dns2.registeredsite.com 207.204.21.31NOERROR, 114 ms, authoritativenono / norefused-
dns3.registeredsite.com 207.204.21.31NOERROR, 114 ms, authoritativenono / norefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: dns1.registeredsite.com (162.214.41.47): read udp 46.225.38.91:42077->162.214.41.47:53: i/o timeout.
    #14
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns2.registeredsite.com (207.204.21.31): dial tcp 207.204.21.31:53: i/o timeout; dns3.registeredsite.com (207.204.21.31): dial tcp 207.204.21.31:53: i/o timeout.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: dns2.registeredsite.com (207.204.21.31), dns3.registeredsite.com (207.204.21.31).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2018072401 · primary dns3.registeredsite.com

Found

Primary (MNAME)
dns3.registeredsite.com
Contact (RNAME)
hostmaster.webcom.com\
Serial
2018072401
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
2560 s

Serial per nameserver

NameserverSerial
dns2.registeredsite.com (207.204.21.31)2018072401
dns3.registeredsite.com (207.204.21.31)2018072401

Checks

  • ✓ Serial 2018072401 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 42m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns3.registeredsite.com is one of the listed nameservers.
  • ✓ Contact hostmaster@webcom.com\ #25
    The SOA RNAME hostmaster.webcom.com\ means hostmaster@webcom.com\ .
  • ✓ Date-based serial #26
    The serial 2018072401 follows the YYYYMMDDnn convention (2018-07-24).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

4 records at the apex

Found

Read from
207.204.21.31:53
TypeValueTTL
SOAdns3.registeredsite.com. hostmaster.webcom.com\ . 2018072401 16384 2048 1048576 25601800
NSdns3.registeredsite.com.86400
NSdns2.registeredsite.com.86400
A209.237.135.69300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35