iyfubh.com

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

Registration

info

.com generic · PDR Ltd. d/b/a PublicDomainRegistry.com · expires 2027-05-24

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
24 May 2017
Last changed
1 July 2026
Expires
24 May 2027
Status
active
Registry nameservers
ns1.nsresolution.com, ns2.nsresolution.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-05-24 #3
    The registration is valid until 2027-05-24 (214 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.nsresolution.com, ns2.nsresolution.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.nsresolution.com, ns2.nsresolution.com
NS in the zone
ns1.nsresolution.com, ns2.nsresolution.com
NameserverAddressesNetwork (AS)Glue
ns1.nsresolution.com208.91.196.46AS40034 CONFLUENCE-NETWORK-INC - Confluence Networks Inc, VG208.91.196.46
ns2.nsresolution.com199.79.60.46AS40034 CONFLUENCE-NETWORK-INC - Confluence Networks Inc, VG199.79.60.46

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.nsresolution.com, ns2.nsresolution.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ 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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS40034 (CONFLUENCE-NETWORK-INC - Confluence Networks Inc, VG): 2 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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nsresolution.com 208.91.196.46NOERROR, 113 ms, authoritativenono / yesrefused-
ns2.nsresolution.com 199.79.60.46NOERROR, 111 ms, authoritativenono / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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: ns1.nsresolution.com (208.91.196.46): dial tcp 208.91.196.46:53: i/o timeout; ns2.nsresolution.com (199.79.60.46): dial tcp 199.79.60.46:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2011062801 · primary ns1.nsresolution.com

Found

Primary (MNAME)
ns1.nsresolution.com
Contact (RNAME)
abuse.confluence-networks.com
Serial
2011062801
Refresh / retry
3600 s / 900 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.nsresolution.com (208.91.196.46)2011062801
ns2.nsresolution.com (199.79.60.46)2011062801

Checks

  • ✓ Serial 2011062801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nsresolution.com is one of the listed nameservers.
  • ✓ Contact abuse@confluence-networks.com #25
    The SOA RNAME abuse.confluence-networks.com means abuse@confluence-networks.com.
  • ✓ Date-based serial #26
    The serial 2011062801 follows the YYYYMMDDnn convention (2011-06-28).

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

6 records at the apex

Found

Read from
208.91.196.46:53
TypeValueTTL
SOAns1.nsresolution.com. abuse.confluence-networks.com. 2011062801 3600 900 604800 86400300
NSns1.nsresolution.com.300
NSns2.nsresolution.com.300
A208.91.196.46900
MX300 ~.3600
TXT"~"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, MX 1h, 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