ahcxgjghdf.com

Checked 22 October 2026, 07:41 UTC · via 8.8.8.8
!Passed with warnings
21 passed 5 warnings 0 failed 5 info

Registration

info

.com generic · Gname.com Pte. Ltd. · expires 2027-08-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Gname.com Pte. Ltd.
Registered
16 August 2023
Last changed
6 October 2026
Expires
16 August 2027
Status
client transfer prohibited
Registry nameservers
a6.share-dns.com, b6.share-dns.net
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-08-16 #3
    The registration is valid until 2027-08-16 (297 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

a6.share-dns.com, b6.share-dns.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a6.share-dns.com, b6.share-dns.net
NS in the zone
a.share-dns.com, b.share-dns.net
NameserverAddressesNetwork (AS)Glue
a.share-dns.com (zone only)172.64.53.25AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
a6.share-dns.com (parent only)172.64.53.25AS13335 CLOUDFLARENET - Cloudflare, Inc., US172.64.53.25
b.share-dns.net (zone only)162.159.27.88AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
b6.share-dns.net (parent only)162.159.27.88AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: a6.share-dns.com, b6.share-dns.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: a6.share-dns.com, b6.share-dns.net; only in the zone: a.share-dns.com, b.share-dns.net. a.share-dns.com, a6.share-dns.com, b.share-dns.net, b6.share-dns.net report NS a.share-dns.com b.share-dns.net.
    #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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a.share-dns.com 172.64.53.25NOERROR, 64 ms, authoritativenoyes / yesrefused2026.10.8
a6.share-dns.com 172.64.53.25NOERROR, 51 ms, authoritativenoyes / yesrefused2026.10.8
b.share-dns.net 162.159.27.88NOERROR, 25 ms, authoritativenoyes / yesrefused2026.10.8
b6.share-dns.net 162.159.27.88NOERROR, 29 ms, authoritativenoyes / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 4 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a.share-dns.com: "2026.10.8"; a6.share-dns.com: "2026.10.8"; b.share-dns.net: "2026.10.8"; b6.share-dns.net: "2026.10.8". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1792063412 · primary a.share-dns.com

Found

Primary (MNAME)
a.share-dns.com
Contact (RNAME)
master.share-dns.com
Serial
1792063412
Refresh / retry
3600 s / 1200 s
Expire
86400 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
a.share-dns.com (172.64.53.25)1792063412
a6.share-dns.com (172.64.53.25)1792063412
b.share-dns.net (162.159.27.88)1792063412
b6.share-dns.net (162.159.27.88)1792063412

Checks

  • ✓ Serial 1792063412 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver a.share-dns.com is one of the listed nameservers.
  • ✓ Contact master@share-dns.com #25
    The SOA RNAME master.share-dns.com means master@share-dns.com.
  • ✓ Timestamp serial #26
    The serial 1792063412 is a Unix timestamp (2026-10-15 11:23 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

4 records at the apex

Found

Read from
172.64.53.25:53
TypeValueTTL
SOAa.share-dns.com. master.share-dns.com. 1792063412 3600 1200 86400 600600
NSa.share-dns.com.86400
NSb.share-dns.net.86400
A177.211.25.215600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, 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.
  • 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