hulkshare.com

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

Registration

info

.com generic · Key-Systems GmbH · expires 2033-08-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Key-Systems GmbH
Registered
3 August 2009
Last changed
30 November 2025
Expires
3 August 2033
Status
client transfer prohibited
Registry nameservers
ns1.hulkshare.com, ns2.hulkshare.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 2033-08-03 #3
    The registration is valid until 2033-08-03 (2477 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

ns1.hulkshare.com, ns2.hulkshare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.hulkshare.com, ns2.hulkshare.com
NS in the zone
ns1.hulkshare.com, ns2.hulkshare.com
NameserverAddressesNetwork (AS)Glue
ns1.hulkshare.com109.201.151.52AS43350 NFORCE - NForce Entertainment B.V., NL109.201.151.52
ns2.hulkshare.com109.201.151.53AS43350 NFORCE - NForce Entertainment B.V., NL109.201.151.53

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.hulkshare.com, ns2.hulkshare.com.
    #6
  • ✓ 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: ns1.hulkshare.com, ns2.hulkshare.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 109.201.151.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS43350 (NFORCE - NForce Entertainment B.V., NL): 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.hulkshare.com 109.201.151.52NOERROR, 9 ms, authoritativenono / yesrefused-
ns2.hulkshare.com 109.201.151.53NOERROR, 9 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.hulkshare.com (109.201.151.52): dial tcp 109.201.151.52:53: connect: connection refused; ns2.hulkshare.com (109.201.151.53): dial tcp 109.201.151.53:53: connect: connection refused.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026061504 · primary ns1.hulkshare.com

Found

Primary (MNAME)
ns1.hulkshare.com
Contact (RNAME)
postmaster.hulkshare.com
Serial
2026061504
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.hulkshare.com (109.201.151.52)2026061504
ns2.hulkshare.com (109.201.151.53)2026061504

Checks

  • ✓ Serial 2026061504 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 10m, expire 7d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.hulkshare.com is one of the listed nameservers.
  • ✓ Contact postmaster@hulkshare.com #25
    The SOA RNAME postmaster.hulkshare.com means postmaster@hulkshare.com.
  • ✓ Date-based serial #26
    The serial 2026061504 follows the YYYYMMDDnn convention (2026-06-15).

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

12 records at the apex

Found

Read from
109.201.151.52:53
TypeValueTTL
SOAns1.hulkshare.com. postmaster.hulkshare.com. 2026061504 3600 600 604800 6086400
NSns2.hulkshare.com.86400
NSns1.hulkshare.com.86400
A109.201.151.63600
A109.201.151.53600
MX5 ALT1.ASPMX.L.GOOGLE.com.3600
MX5 ALT2.ASPMX.L.GOOGLE.com.3600
MX10 ASPMX2.GOOGLEMAIL.com.3600
MX10 ASPMX3.GOOGLEMAIL.com.3600
MX1 ASPMX.L.GOOGLE.com.3600
TXT"v=spf1 include:_spf.google.com include:spf.smtp2go.com ip4:109.201.151.3 ip4:109.201.151.4 ip4:109.201.151.5 ip4:109.201.151.6 ip4:109.201.151.7 ip4:109.201.151.35 ~all"86400
TXT"google-site-verification=wOieo_6W1USG82Dzhc36wmZ8YKk6vHyrA6-0Y6WWEb4"86400

Checks

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