Domain report: xlx870.nl

Registration

info

.nl country-code

Found

TLD: .nl (country-code)
ICANN policies apply: no

Lookup error: https://rdap.sidn.nl/domain/xlx870.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/xlx870.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

Nameserver	Addresses	Network (AS)	Glue
ns1.mijn.host	5.254.117.200 2a03:5180:7:2:13af:27fb:f741:1	AS3223 VOXILITY - Voxility LLP, GB AS3223 VOXILITY - Voxility LLP, GB	-
ns2.mijn.host	217.180.14.14 2a11:4881:1:4881::1	AS214673 mijnhost - mijn.host B.V., NL AS214673 mijnhost - mijn.host B.V., NL	-
ns3.mijn.host	83.96.241.95 2a02:348:5e6:1::b6a0	AS35470 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

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.mijn.host 5.254.117.200	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns1.mijn.host 2a03:5180:7:2:13af:27fb:f741:1	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns2.mijn.host 217.180.14.14	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns2.mijn.host 2a11:4881:1:4881::1	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns3.mijn.host 83.96.241.95	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-
ns3.mijn.host 2a02:348:5e6:1::b6a0	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-

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 1790368229 · primary ns1.mijn.host

Found

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

Serial per nameserver

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

Checks

✓ Serial 1790368229 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@xlx870.nl #25

The SOA RNAME hostmaster.xlx870.nl means hostmaster@xlx870.nl.
✓ Timestamp serial #26

The serial 1790368229 is a Unix timestamp (2026-09-25 20:30 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 tag	Algorithm	Digest	Matches a key
11457	ECDSAP256SHA256 (13)	SHA256 DC7A95BE9B9CD363…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
11457	KSK (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 11457 (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

Type	Value	TTL
SOA	ns1.mijn.host. hostmaster.xlx870.nl. 1790368229 10800 3600 604800 3600	3600
NS	ns2.mijn.host.	900
NS	ns1.mijn.host.	900
NS	ns3.mijn.host.	900
A	5.254.124.136	900
AAAA	2001:67c:b30:131::1	900
MX	10 h15.mijn.host.	900
TXT	"v=spf1 a mx include:spf.mijn.host ~all"	900
CAA	0 issue "letsencrypt.org"	900

Checks

✓ TTLs within range #32

TTLs: A 15m, AAAA 15m, MX 15m, NS 15m. The NS TTL at the parent is 1h and in the zone 15m; 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: letsencrypt.org.