Domain report: ed.nl

Registration

info

.nl country-code · Registrar.eu

Found

TLD: .nl (country-code)
ICANN policies apply: no
Registrar: Registrar.eu
Registered: 3 March 1997
Last changed: 1 October 2026
Status: active
Registry nameservers: eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net
RDAP server: https://rdap.sidn.nl/

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

Expiry date not published

The registry does not publish the expiry date in RDAP. Check it with your registrar.

#3
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

eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net
NS in the zone: eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net

Nameserver	Addresses	Network (AS)	Glue
eur2.akam.net	95.100.173.64	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
eur5.akam.net	23.74.25.64	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
eur6.akam.net	2.22.230.64	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
ns1-125.akam.net	193.108.91.125 2600:1401:2::7d	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
ns1-25.akam.net	193.108.91.25 2600:1401:2::19	AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
usc2.akam.net	184.26.160.64	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
use2.akam.net	96.7.49.64	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
use5.akam.net	2.16.40.64 2600:1403:a::40	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-

Checks

✓ 8 nameservers #6

Delegated to eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.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 7 IPv4 /24s and 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 10 addresses.
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
i

Partly IPv6

These nameservers have no IPv6 address: eur2.akam.net, eur5.akam.net, eur6.akam.net, usc2.akam.net, use2.akam.net.

#13

Nameservers

warn

11 of 11 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
eur2.akam.net 95.100.173.64	NOERROR, 3 ms, authoritative	no	yes / yes	refused	48878.33
eur5.akam.net 23.74.25.64	NOERROR, 3 ms, authoritative	no	yes / yes	refused	48878.31
eur6.akam.net 2.22.230.64	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.4
ns1-125.akam.net 193.108.91.125	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.7
ns1-125.akam.net 2600:1401:2::7d	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.11
ns1-25.akam.net 193.108.91.25	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.4
ns1-25.akam.net 2600:1401:2::19	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.11
usc2.akam.net 184.26.160.64	NOERROR, 3 ms, authoritative	no	yes / yes	refused	48878.33
use2.akam.net 96.7.49.64	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.7
use5.akam.net 2.16.40.64	NOERROR, 3 ms, authoritative	no	yes / yes	refused	48878.27
use5.akam.net 2600:1403:a::40	NOERROR, 3 ms, authoritative	no	yes / yes	refused	48878.29

Checks

✓ All respond #14

All 11 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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: eur2.akam.net: "48878.33"; eur5.akam.net: "48878.31"; eur6.akam.net: "41824.4"; ns1-125.akam.net: "41824.7"; ns1-125.akam.net: "41824.11"; ns1-25.akam.net: "41824.4"; ns1-25.akam.net: "41824.11"; usc2.akam.net: "48878.33"; use2.akam.net: "41824.7"; use5.akam.net: "48878.27"; use5.akam.net: "48878.29". Hide or replace the version string.

#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

warn

serial 353 · primary ns1-25.akam.net

Found

Primary (MNAME): ns1-25.akam.net
Contact (RNAME): hostmaster.persgroep.be
Serial: 353
Refresh / retry: 900 s / 600 s
Expire: 1209600 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
eur2.akam.net (95.100.173.64)	353
eur5.akam.net (23.74.25.64)	353
eur6.akam.net (2.22.230.64)	353
ns1-125.akam.net (193.108.91.125)	353
ns1-125.akam.net (2600:1401:2::7d)	353
ns1-25.akam.net (193.108.91.25)	353
ns1-25.akam.net (2600:1401:2::19)	353
usc2.akam.net (184.26.160.64)	353
use2.akam.net (96.7.49.64)	353
use5.akam.net (2.16.40.64)	353
use5.akam.net (2600:1403:a::40)	353

Checks

✓ Serial 353 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 14d, negative TTL 5m.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns1-25.akam.net is one of the listed nameservers.
✓ Contact hostmaster@persgroep.be #25

The SOA RNAME hostmaster.persgroep.be means hostmaster@persgroep.be.
✓ Counter serial #26

The serial 353 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 0 iterations, 0-byte salt
Signatures valid until: 24 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
28221	ECDSAP256SHA256 (13)	SHA256 5A5F713F9F5C9CC3…	NO
2741	ECDSAP256SHA256 (13)	SHA256 D943E8C4C5B1D34A…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
54535	ZSK (256)	ECDSAP256SHA256 (13)
26180	ZSK (256)	ECDSAP256SHA256 (13)
2741	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.
i

Unused DS records

These DS records match no key in the zone: key tag 28221 (SHA256). That is normal during a key rollover; otherwise remove them.

#28
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13).
✓ Short-lived signatures (online signing) #30

Signatures are valid for 73h0m0s and created on demand; the current one was made at 2026-10-21 13:11 UTC and expires at 2026-10-24 14:11 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

31 records at the apex

Found

Read from: 95.100.173.64:53

Type	Value	TTL
SOA	ns1-25.akam.net. hostmaster.persgroep.be. 353 900 600 1209600 300	900
NS	ns1-125.akam.net.	900
NS	use2.akam.net.	900
NS	use5.akam.net.	900
NS	usc2.akam.net.	900
NS	eur5.akam.net.	900
NS	eur6.akam.net.	900
NS	ns1-25.akam.net.	900
NS	eur2.akam.net.	900
A	2.16.204.15	20
A	2.16.204.16	20
AAAA	2a02:26f0:b700:5::210:cc0f	20
AAAA	2a02:26f0:b700:5::210:cc10	20
MX	5 alt1.aspmx.l.google.com.	3600
MX	1 aspmx.l.google.com.	3600
MX	5 alt2.aspmx.l.google.com.	3600
MX	10 alt4.aspmx.l.google.com.	3600
MX	10 alt3.aspmx.l.google.com.	3600
TXT	"klaviyo-site-verification=TZVDvP"	900
TXT	"v=spf1 ip4:146.185.48.0/21 include:_spf.google.com ip4:83.96.149.124 ip4:162.13.81.10 ip4:194.26.137.0/24 ip4:82.94.214.0/24 ip4:46.21.234.32/27 ip4:87.233.77.245 ip4:46.21.235.128/26 ip4:46.21.235.192/26 ip4:217.68.27.250" " ip4:217.68.27.206 ip4:194.88.230.32/27 ip4:194.88.231.0/24 ip4:80.69.72.128/28 ip4:87.253.151.0/24 ip4:79.143.217.1/24 ip4:87.233.195.0/24 ip4:87.233.192.0/24 include:_spf.relay.mailprotect.be include:spf.flowmailer.net include:spf.mailjet.com ~all"	900
TXT	"google-site-verification=O4mw8WHtUjR8CYdOmiNbyNhyX75vFTpKDq2DDVvzUdk"	900
TXT	"google-site-verification=dgTMtCmslV2TM7Ex5ylu60O47mKVVFgWXGocPyX1OMU"	900
TXT	"spf2.0/pra,mfrom" "mx" "ip4:83.96.149.124" "ip4:194.26.137.0/24" "include:spf.e-ngine.nl" "include:_spf.google.com" "~all"	900
TXT	"facebook-domain-verification=lvdla9q5rh9oc4svj9udtgigmg94te"	900
TXT	"fcnPcz7mIshZAFd6DwTmUoZ7a85NXuyNo+hJWnE2QvPi7eE2kH5sWTRBxptDjTvRuapc4xx6n/GyhvCksThbqw=="	900
TXT	"google-site-verification=1eBIs4poZgy93y7gkEPeNYWFS6C_M7YNr1e9GhsO8Ko"	900
TXT	"MS=ms10453340"	900
TXT	"google-site-verification=jBqTI_iaqtmYeeRwZHJj9w3-GC-3TQmVIlqbJPG5FYQ"	900
TXT	"persgroep-ecommerce-prod.azurewebsites.net"	900
TXT	"facebook-domain-verification=oqgdgrmafq5w0jpnyvac6vre4c99bo"	900
TXT	"atlassian-domain-verification=gqfC576h6pKDntEMQCdrUMXTtOD2vfhKvXTSXAIxiT3BSdIBLzbPWwOkt0jwiITX"	900

Checks

!

Very low TTLs

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

#32
✓ No CNAME at the apex #33

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

Names that don't exist return NXDOMAIN.
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