dpgmedia.nl

Checked 21 October 2026, 21:15 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 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/dpgmedia.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/dpgmedia.nl returned HTTP 429
    #3

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
NameserverAddressesNetwork (AS)Glue
eur2.akam.net95.100.173.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur5.akam.net23.74.25.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur6.akam.net2.22.230.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-125.akam.net193.108.91.125 2600:1401:2::7dAS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-25.akam.net193.108.91.25 2600:1401:2::19AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usc2.akam.net184.26.160.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use2.akam.net96.7.49.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use5.akam.net2.16.40.64 2600:1403:a::40AS21342 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

NameserverAnswerRecursionTCP / EDNSAXFRVersion
eur2.akam.net 95.100.173.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
eur5.akam.net 23.74.25.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.27
eur6.akam.net 2.22.230.64NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
ns1-125.akam.net 193.108.91.125NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
ns1-125.akam.net 2600:1401:2::7dNOERROR, 4 ms, authoritativenoyes / yesrefused41824.6
ns1-25.akam.net 193.108.91.25NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
ns1-25.akam.net 2600:1401:2::19NOERROR, 4 ms, authoritativenoyes / yesrefused41824.5
usc2.akam.net 184.26.160.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.30
use2.akam.net 96.7.49.64NOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
use5.akam.net 2.16.40.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.31
use5.akam.net 2600:1403:a::40NOERROR, 3 ms, authoritativenoyes / yesrefused48878.27

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.32"; eur5.akam.net: "48878.27"; eur6.akam.net: "41824.10"; ns1-125.akam.net: "41824.10"; ns1-125.akam.net: "41824.6"; ns1-25.akam.net: "41824.10"; ns1-25.akam.net: "41824.5"; usc2.akam.net: "48878.30"; use2.akam.net: "41824.4"; use5.akam.net: "48878.31"; use5.akam.net: "48878.27". 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

pass

serial 776 · primary ns1-25.akam.net

Found

Primary (MNAME)
ns1-25.akam.net
Contact (RNAME)
hostmaster.persgroep.be
Serial
776
Refresh / retry
7200 s / 3600 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

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

Checks

  • ✓ Serial 776 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 1h, expire 14d, negative TTL 5m.
  • ✓ 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 776 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 tagAlgorithmDigestMatches a key
16598ECDSAP256SHA256 (13)SHA256 34FED7FE82C810F1…yes
42191ECDSAP256SHA256 (13)SHA256 B29E711E146C162E…NO

DNSKEY in the zone

Key tagRoleAlgorithm
16598KSK (257)ECDSAP256SHA256 (13)
48210ZSK (256)ECDSAP256SHA256 (13)
53037ZSK (256)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 42191 (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:03 UTC and expires at 2026-10-24 14:03 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

39 records at the apex

Found

Read from
95.100.173.64:53
TypeValueTTL
SOAns1-25.akam.net. hostmaster.persgroep.be. 776 7200 3600 1209600 300900
NSuse2.akam.net.900
NSns1-25.akam.net.900
NSuse5.akam.net.900
NSeur6.akam.net.900
NSns1-125.akam.net.900
NSusc2.akam.net.900
NSeur5.akam.net.900
NSeur2.akam.net.900
A2.16.204.2420
A2.16.204.1020
AAAA2a02:26f0:b700:5::210:cc0a20
AAAA2a02:26f0:b700:5::210:cc1820
MX10 aspmx2.googlemail.com.900
MX5 alt1.aspmx.l.google.com.900
MX5 alt2.aspmx.l.google.com.900
MX10 aspmx3.googlemail.com.900
MX1 aspmx.l.google.com.900
TXT"google-site-verification=OFuT0sku1FNyBn8NGNrWIYeMnBxdj3Cw8RnmPKTF3mg"300
TXT"_globalsign-domain-verification=Oq6NKVBlI5zFkmVbiHpDvh43BHnogvLZ3krBbrIKaP"300
TXT"jamf-site-verification=I5W-OlREZYbAJt7vX2HIqA"300
TXT"knowbe4-site-verification=5cb3e34fa04a4787857ac35a00fa9327"300
TXT"MS=ms42017178"300
TXT"apple-domain-verification=rhgBCR84l7Uc5cMp"300
TXT"v=spf1 ip4:146.185.48.0/21 ip4:145.60.8.129 include:_spf.google.com include:spf.protection.outlook.com " "include:et._spf.pardot.com include:_spf.salesforce.com include:spf1.dpgmedia.nl include:spf2.dpgmedia.nl include:mail.zendesk.com include:spf.crowdtech.com -all"300
TXT"google-site-verification=L7RecrH5RTtWIgjCAdqoKi8GHMgoCtfPMk1MQ-_A61A"300
TXT"globalsign-domain-verification=fxO-oZ6xBPNZcHaVlYx6ceobJ6drHbywrgO8594L_X"300
TXT"sending_domain732773=4145824b50bd3c863708192035a68a9eab50638068331aca2574276aef180bd5"300
TXT"atlassian-domain-verification=gqfC576h6pKDntEMQCdrUMXTtOD2vfhKvXTSXAIxiT3BSdIBLzbPWwOkt0jwiITX"300
TXT"google-site-verification=HCULTGPeBKe3q6PXsdBGZwX_u9vcLA5Ag5MK6S6FFlI"300
TXT"globalsign-domain-verification=1KuEjPzNgHZNa8L1RDGUsijACQXYuKSX0iRE-IgMbM"300
TXT"pardot396912=d103e8fb586b4ea12a5eef9ab8db50f225ffa9534121042c3c6f19110507cc0d"300
TXT"globalsign-domain-verification=D8tRjhFB3jo9I1zhzbeimuR1ZZFWeM3TdNy9K1TY8G"300
TXT"google-site-verification=9BOW7AtoeMAiQCOR3Zsi_u62trb62MCyyPQvoEOLnmg"300
TXT"google-site-verification=BS9bRgQCaGMV-qV7KXIW3k9PKEroMT8ZkO9SXCCupe8"300
TXT"atlassian-domain-verification=ssHGvZHDdS5FmfVQpIMaFz7N72WfDW4eBo9yqtYNFjK/GIpJ1yW8IiERm5km/bSj"300
TXT"miro-verification=6ab58ecb32755bd8fe2c2255f7fce54a0f770a62"300
TXT"_globalsign-domain-verification=nsqnD7wwhGNdAOhsaYaOrHYUUv235YiSl78GYluXBl"300
TXT"docker-verification=95c9e864-d269-4fa1-bb5e-e34fccc6288d"300

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