hpage.com

Checked 22 October 2026, 09:13 UTC · via 8.8.8.8
!Passed with warnings
24 passed 1 warning 0 failed 6 info

Registration

info

.com generic · Mesh Digital Limited · expires 2027-05-22

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Mesh Digital Limited
Registered
22 May 2004
Last changed
21 May 2026
Expires
22 May 2027
Status
active
Registry nameservers
ns1.nodesecure.com, ns2.nodesecure.de
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-22 #3
    The registration is valid until 2027-05-22 (212 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

info

ns1.nodesecure.com, ns2.nodesecure.de

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.nodesecure.com, ns2.nodesecure.de
NS in the zone
ns1.nodesecure.com, ns2.nodesecure.de
NameserverAddressesNetwork (AS)Glue
ns1.nodesecure.com192.174.68.102 2001:67c:1bc::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT192.174.68.102 2001:67c:1bc::102
ns2.nodesecure.de176.97.158.102 2001:67c:10b8::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.nodesecure.com, ns2.nodesecure.de.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 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, .de.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nodesecure.com 192.174.68.102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.nodesecure.com 2001:67c:1bc::102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.nodesecure.de 176.97.158.102NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.nodesecure.de 2001:67c:10b8::102NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.nodesecure.com: "RcodeZero DNS"; ns2.nodesecure.de: "reg-wie1".
    #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

pass

serial 2026101900 · primary ns1.nodesecure.com

Found

Primary (MNAME)
ns1.nodesecure.com
Contact (RNAME)
hostmaster.hpage.com
Serial
2026101900
Refresh / retry
3600 s / 1800 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.nodesecure.com (192.174.68.102)2026101900
ns1.nodesecure.com (2001:67c:1bc::102)2026101900
ns2.nodesecure.de (176.97.158.102)2026101900
ns2.nodesecure.de (2001:67c:10b8::102)2026101900

Checks

  • ✓ Serial 2026101900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nodesecure.com is one of the listed nameservers.
  • ✓ Contact hostmaster@hpage.com #25
    The SOA RNAME hostmaster.hpage.com means hostmaster@hpage.com.
  • ✓ Date-based serial #26
    The serial 2026101900 follows the YYYYMMDDnn convention (2026-10-19).

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

13 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAns1.nodesecure.com. hostmaster.hpage.com. 2026101900 3600 1800 604800 600600
NSns1.nodesecure.com.600
NSns2.nodesecure.de.600
A85.190.0.100600
AAAA2001:1bc0:ad::d100600
MX1 aspmx.l.google.com.600
MX5 alt1.aspmx.l.google.com.600
MX5 alt2.aspmx.l.google.com.600
MX10 alt3.aspmx.l.google.com.600
MX10 alt4.aspmx.l.google.com.600
TXT"site24x7-signals-domain-verification=be9cf2fb8905def739a2c81e18796416"600
TXT"v=spf1 mx ip4:85.190.0.100 mx:mail-in.hpage.com include:mail.zendesk.com include:_spf.google.com include:sendgrid.net -all"600
CAA0 iodef "mailto:hostmaster@hpage.com"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, MX 10m, NS 10m. The NS TTL at the parent is 2d and in the zone 10m; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: .