mysite.com

Checked 22 October 2026, 09:54 UTC · via 8.8.8.8
✗Problems found
21 passed 4 warnings 1 failed 5 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-10-26

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
7 September 1995
Last changed
22 October 2026
Expires
26 October 2027
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
authns-ws.dca.mysite.com, authns-ws.iad.mysite.com, authns-ws.vgs.mysite.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 2027-10-26 #3
    The registration is valid until 2027-10-26 (369 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

authns-ws.dca.mysite.com, authns-ws.iad.mysite.com, authns-ws.vgs.mysite.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
authns-ws.dca.mysite.com, authns-ws.iad.mysite.com, authns-ws.vgs.mysite.com
NS in the zone
authns-ws.dca.mysite.com, authns-ws.iad.mysite.com, authns-ws.vgs.mysite.com
NameserverAddressesNetwork (AS)Glue
authns-ws.dca.mysite.com64.136.44.123AS13446 AS-NETZERO - Netzero,INC., US64.136.44.123
authns-ws.iad.mysite.com64.136.25.254AS13446 AS-NETZERO - Netzero,INC., US64.136.25.254
authns-ws.vgs.mysite.com64.136.20.20AS13446 AS-NETZERO - Netzero,INC., US64.136.20.20

Checks

  • ✓ 3 nameservers #6
    Delegated to authns-ws.dca.mysite.com, authns-ws.iad.mysite.com, authns-ws.vgs.mysite.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: authns-ws.dca.mysite.com, authns-ws.iad.mysite.com, authns-ws.vgs.mysite.com.
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13446 (AS-NETZERO - Netzero,INC., US): 3 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
authns-ws.dca.mysite.com 64.136.44.123NOERROR, 105 ms, authoritativenono / norefused-
authns-ws.iad.mysite.com 64.136.25.254NOERROR, 143 ms, authoritativenono / norefused-
authns-ws.vgs.mysite.com 64.136.20.20NOERROR, 143 ms, authoritativenono / norefused-

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✓ 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: authns-ws.dca.mysite.com (64.136.44.123): dial tcp 64.136.44.123:53: connect: connection refused; authns-ws.iad.mysite.com (64.136.25.254): dial tcp 64.136.25.254:53: connect: connection refused; authns-ws.vgs.mysite.com (64.136.20.20): dial tcp 64.136.20.20:53: connect: connection refused.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: authns-ws.dca.mysite.com (64.136.44.123), authns-ws.iad.mysite.com (64.136.25.254), authns-ws.vgs.mysite.com (64.136.20.20).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1791948734 · primary authns-ws.vgs.mysite.com

Found

Primary (MNAME)
authns-ws.vgs.mysite.com
Contact (RNAME)
hostmaster.noc.untd.com
Serial
1791948734
Refresh / retry
300 s / 300 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
authns-ws.dca.mysite.com (64.136.44.123)1791948734
authns-ws.iad.mysite.com (64.136.25.254)1791948734
authns-ws.vgs.mysite.com (64.136.20.20)1791948734

Checks

  • ✓ Serial 1791948734 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m. Current values: refresh 5m, retry 5m, expire 7d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver authns-ws.vgs.mysite.com is one of the listed nameservers.
  • ✓ Contact hostmaster@noc.untd.com #25
    The SOA RNAME hostmaster.noc.untd.com means hostmaster@noc.untd.com.
  • ✓ Timestamp serial #26
    The serial 1791948734 is a Unix timestamp (2026-10-14 03:32 UTC).

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

8 records at the apex

Found

Read from
64.136.44.123:53
TypeValueTTL
SOAauthns-ws.vgs.mysite.com. hostmaster.noc.untd.com. 1791948734 300 300 604800 3001200
NSauthns-ws.dca.mysite.com.300
NSauthns-ws.iad.mysite.com.300
NSauthns-ws.vgs.mysite.com.300
A64.136.20.67300
MX1 mx.vgs.untd.com.300
MX1 mx.dca.untd.com.300
TXT"6au9h04p908vks6j39q1223opu"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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