Domain report: mcvoordieren.nl

Registration

info

.nl country-code

Found

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

Lookup error: https://rdap.sidn.nl/domain/mcvoordieren.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/mcvoordieren.nl returned HTTP 429

#3

Delegation

pass

ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net
NS in the zone: ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net

Nameserver	Addresses	Network (AS)	Glue
ns3.firstfind.nl	5.157.86.222 2a01:b940:1057::53	AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL	-
ns4.firstfind.nl	5.157.87.222 2a01:b940:1057::54	AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL	-
ns5.firstfind.net	178.128.248.2 2a03:b0c0:2:d0::1183:f001	AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US	-

Checks

✓ 3 nameservers #6

Delegated to ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net.
✓ 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 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS48635 (CLDIN-NL - Your Hosting B.V., NL): 4 addresses.
✓ Nameserver names under 2 TLDs #12

Nameserver names use the TLDs .net, .nl.
✓ 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
ns3.firstfind.nl 5.157.86.222	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns3.firstfind.nl 2a01:b940:1057::53	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns4.firstfind.nl 5.157.87.222	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns4.firstfind.nl 2a01:b940:1057::54	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns5.firstfind.net 178.128.248.2	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns5.firstfind.net 2a03:b0c0:2:d0::1183:f001	NOERROR, 15 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 2026102201 · primary ns3.firstfind.nl

Found

Primary (MNAME): ns3.firstfind.nl
Contact (RNAME): hostmaster.firstfind.nl
Serial: 2026102201
Refresh / retry: 16384 s / 2048 s
Expire: 1048576 s
Negative TTL: 14400 s

Serial per nameserver

Nameserver	Serial
ns3.firstfind.nl (5.157.86.222)	2026102201
ns3.firstfind.nl (2a01:b940:1057::53)	2026102201
ns4.firstfind.nl (5.157.87.222)	2026102201
ns4.firstfind.nl (2a01:b940:1057::54)	2026102201
ns5.firstfind.net (178.128.248.2)	2026102201
ns5.firstfind.net (2a03:b0c0:2:d0::1183:f001)	2026102201

Checks

✓ Serial 2026102201 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 4h.
✓ Primary is a public nameserver #24

The primary nameserver ns3.firstfind.nl is one of the listed nameservers.
✓ Contact hostmaster@firstfind.nl #25

The SOA RNAME hostmaster.firstfind.nl means hostmaster@firstfind.nl.
✓ Date-based serial #26

The serial 2026102201 follows the YYYYMMDDnn convention (2026-10-22).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver: yes
NSEC3: 1 iterations, 1-byte salt
Signatures valid until: 5 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
22159	RSASHA256 (8)	SHA256 C5ECA352BDB608F0…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
22159	KSK (257)	RSASHA256 (8)
50904	ZSK (256)	RSASHA256 (8)

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 22159 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-05 #30

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.

Records

warn

8 records at the apex

Found

Read from: 5.157.86.222:53

Type	Value	TTL
SOA	ns3.firstfind.nl. hostmaster.firstfind.nl. 2026102201 16384 2048 1048576 14400	100
NS	ns4.firstfind.nl.	100
NS	ns3.firstfind.nl.	100
NS	ns5.firstfind.net.	100
A	45.82.191.16	60
MX	0 mcvoordieren-nl.i-v1.mx.microsoft.	300
TXT	"MS=ms79715698"	60
TXT	"v=spf1 include:_spf.yourfilter.nl include:spf.protection.outlook.com include:webmail.mcvoordieren.nl include:_spf.inboxify.nl a mx ip4:81.173.68.37 ip4:81.173.68.38 ip4:81.173.126.141 ip4:109.235.32.68 ip4:45.82.191.16 ip4:85.17.142.79 ip4:37.152.9.237 ~a" "ll"	60

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), NS (1m40s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m40s; resolvers may use either.

#32
✓ 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