princessehof.nl

Checked 22 October 2026, 15:21 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 warnings 0 failed 6 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/princessehof.nl returned HTTP 429

Checks

  • i
    .nl is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .nl is delegated in the root zone and DNSSEC-signed.
  • i
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/princessehof.nl returned HTTP 429
    #3

Delegation

info

ns1.mijn.host, ns2.mijn.host, ns3.mijn.host

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.mijn.host, ns2.mijn.host, ns3.mijn.host
NS in the zone
ns1.mijn.host, ns2.mijn.host, ns3.mijn.host
NameserverAddressesNetwork (AS)Glue
ns1.mijn.host5.254.117.200 2a03:5180:7:2:13af:27fb:f741:1AS3223 VOXILITY - Voxility LLP, GB AS3223 VOXILITY - Voxility LLP, GB-
ns2.mijn.host217.180.14.14 2a11:4881:1:4881::1AS214673 mijnhost - mijn.host B.V., NL AS214673 mijnhost - mijn.host B.V., NL-
ns3.mijn.host83.96.241.95 2a02:348:5e6:1::b6a0AS35470 XL-AS - Signet B.V., NL AS35470 XL-AS - Signet B.V., NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.mijn.host, ns2.mijn.host, ns3.mijn.host.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS214673 (mijnhost - mijn.host B.V., NL): 2 addresses; AS3223 (VOXILITY - Voxility LLP, GB): 2 addresses; AS35470 (XL-AS - Signet B.V., NL): 2 addresses.
  • i
    All nameserver names under .host
    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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.mijn.host 5.254.117.200NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns1.mijn.host 2a03:5180:7:2:13af:27fb:f741:1NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.mijn.host 217.180.14.14NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.mijn.host 2a11:4881:1:4881::1NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns3.mijn.host 83.96.241.95NOERROR, 19 ms, authoritativenoyes / yesrefused-
ns3.mijn.host 2a02:348:5e6:1::b6a0NOERROR, 13 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ 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 1781002972 · primary ns1.mijn.host

Found

Primary (MNAME)
ns1.mijn.host
Contact (RNAME)
hostmaster.princessehof.nl
Serial
1781002972
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.mijn.host (5.254.117.200)1781002972
ns1.mijn.host (2a03:5180:7:2:13af:27fb:f741:1)1781002972
ns2.mijn.host (217.180.14.14)1781002972
ns2.mijn.host (2a11:4881:1:4881::1)1781002972
ns3.mijn.host (83.96.241.95)1781002972
ns3.mijn.host (2a02:348:5e6:1::b6a0)1781002972

Checks

  • ✓ Serial 1781002972 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.mijn.host is one of the listed nameservers.
  • ✓ Contact hostmaster@princessehof.nl #25
    The SOA RNAME hostmaster.princessehof.nl means hostmaster@princessehof.nl.
  • ✓ Timestamp serial #26
    The serial 1781002972 is a Unix timestamp (2026-06-09 11:02 UTC).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
41859ECDSAP256SHA256 (13)SHA256 DB6D8A892E899E27…yes

DNSKEY in the zone

Key tagRoleAlgorithm
41859KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 41859 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

9 records at the apex

Found

Read from
5.254.117.200:53
TypeValueTTL
SOAns1.mijn.host. hostmaster.princessehof.nl. 1781002972 10800 3600 604800 36003600
NSns2.mijn.host.3600
NSns3.mijn.host.3600
NSns1.mijn.host.3600
A37.97.250.160900
AAAA2a01:7c8:fffa:18a::1900
MX10 princessehof-nl.mail.protection.outlook.com.900
TXT"v=spf1 include:spf.protection.outlook.com +ip4:37.97.250.180 +ip4:185.133.88.24 +ip4:82.94.205.36 a:mailing.ticketteam.cloud +ip4:192.87.104.130 +ip4:185.250.160.112 +ip6:2a02:5b0:125:200:185:250:160:112 +ip6:2a01:7c8:fffa:193::1 -all"900
TXT"MS=ms78416735"900

Checks

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