Domain report: simyo.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

info

ns13.kpn.net, ns3.kpn.net

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns13.kpn.net	213.75.63.34 2a02:a47f:ac:1::1353	AS1136 KPN - KPN B.V., NL AS1136 KPN - KPN B.V., NL	-
ns3.kpn.net	194.151.228.42 2a02:a47f:ac:1::353	AS1136 KPN - KPN B.V., NL AS1136 KPN - KPN B.V., NL	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns13.kpn.net, ns3.kpn.net.

#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.
i

One address family in one network

all IPv6 addresses are in 2a02:a47f:ac::/48, while the other address family is spread over several networks.

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS1136 (KPN - KPN B.V., NL): 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
i

All nameserver names under .net

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

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns13.kpn.net 213.75.63.34	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns13.kpn.net 2a02:a47f:ac:1::1353	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns3.kpn.net 194.151.228.42	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns3.kpn.net 2a02:a47f:ac:1::353	NOERROR, 14 ms, authoritative	no	yes / yes	refused	-

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.
✓ 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.kpn.net

Found

Primary (MNAME): ns3.kpn.net
Contact (RNAME): zonemaster.kpn.com
Serial: 2026102201
Refresh / retry: 10800 s / 3600 s
Expire: 604800 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ns13.kpn.net (213.75.63.34)	2026102201
ns13.kpn.net (2a02:a47f:ac:1::1353)	2026102201
ns3.kpn.net (194.151.228.42)	2026102201
ns3.kpn.net (2a02:a47f:ac:1::353)	2026102201

Checks

✓ Serial 2026102201 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 ns3.kpn.net is one of the listed nameservers.
✓ Contact zonemaster@kpn.com #25

The SOA RNAME zonemaster.kpn.com means zonemaster@kpn.com.
✓ Date-based serial #26

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

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
2382	ECDSAP256SHA256 (13)	SHA256 14E52F30F1978E9A…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
2382	KSK (257)	ECDSAP256SHA256 (13)
39642	ZSK (256)	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 2382 (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

warn

19 records at the apex

Found

Read from: 213.75.63.34:53

Type	Value	TTL
SOA	ns3.kpn.net. zonemaster.kpn.com. 2026102201 10800 3600 604800 3600	3600
NS	ns13.kpn.net.	3600
NS	ns3.kpn.net.	3600
A	76.223.42.229	900
A	15.197.78.208	900
MX	10 simyo-nl.mail.protection.outlook.com.	60
TXT	"UcIHTl8sFefN6EXTDl6WcEHoTcTPDMsav2y8FBgMbzNYkf99eJyaGqIPoCxw9zDa"	3600
TXT	"jgMdaikV82szhSFgCA0cyQo3NkhJmYz3WNUGDq6Xa1UiSlQ32iI2ELU7A5WwhTX5"	3600
TXT	"BIkbRBfdKRw2oKBQVKEcOOYY16SMLeMtAKmNByogVHA3xq8XdSM3Xy7BNdXDO3Fm"	3600
TXT	"MS=ms29621717"	3600
TXT	"oRIoi5oCZACJof73Hq22XAwMjOTeoSmkuSmHL4YLAr0EGeBD1skdjdjHGBCGWJWu"	3600
TXT	"4HWwaus1GzI7FThXDQyTPPBWgp3P6yS49L3DbDl4zMiVLscS7ZgvHkcj8Ymf3l5O"	3600
TXT	"v=spf1 ip4:185.151.220.50 ip4:217.149.72.102 ip4:213.75.38.161 ip4:213.75.38.162 ip4:213.75.38.71 ip4:213.75.38.72 ip4:213.75.38.73 include:msdp1.com include:spf.mandrillapp.com include:spf.omnidesk.io include:spf.classified.safemail.kpn.com a mx ~all"	3600
TXT	"7b033faed16a0dc41c78e77987bce95f"	3600
CAA	0 issue "letsencrypt.org"	900
CAA	0 issue "certsign.ro"	900
CAA	0 issue "kpn.com"	900
CAA	0 issue "amazonaws.com"	900
CAA	0 iodef "mailto:abuse@kpn.com"	900

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change.

#32
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
✓ No wildcard #34

Names that don't exist return NXDOMAIN.
✓ CAA restricts issuance #35

Certificates may be issued by: letsencrypt.org, certsign.ro, kpn.com, amazonaws.com.