plieger.nl

Checked 22 October 2026, 15:12 UTC · via 8.8.8.8
✗Problems found
15 passed 6 warnings 1 failed 7 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/plieger.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/plieger.nl returned HTTP 429
    #3

Delegation

fail

ns11.pliegergroep.it, ns12.pliegergroep.it

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns11.pliegergroep.it, ns12.pliegergroep.it
NS in the zone
ns11.pliegergroep.it, ns12, ns12.pliegergroep.it
NameserverAddressesNetwork (AS)Glue
ns11.pliegergroep.it89.20.180.74AS39686 AS-EUROFIBER - Eurofiber Nederland BV, NL-
ns12 (zone only)(does not resolve)-
ns12.pliegergroep.it89.20.180.3AS39686 AS-EUROFIBER - Eurofiber Nederland BV, NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns11.pliegergroep.it, ns12.pliegergroep.it.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns12. ns12.pliegergroep.it report NS ns11.pliegergroep.it ns12 ns12.pliegergroep.it.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns12.
    #9
  • !
    Nameservers in one network
    all IPv4 addresses are in 89.20.180.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS39686 (AS-EUROFIBER - Eurofiber Nederland BV, NL): 2 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 .it
    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: ns11.pliegergroep.it, ns12.pliegergroep.it.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns11.pliegergroep.it 89.20.180.74NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns12.pliegergroep.it 89.20.180.3NOERROR, 13 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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

warn

serial 2005120950 · primary ns11.pliegergroep.it

Found

Primary (MNAME)
ns11.pliegergroep.it
Contact (RNAME)
hostmaster.pliegergroep.it
Serial
2005120950
Refresh / retry
60 s / 60 s
Expire
60 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns11.pliegergroep.it (89.20.180.74)2005120950
ns12.pliegergroep.it (89.20.180.3)2005120938

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2005120938 on ns12.pliegergroep.it (89.20.180.3); 2005120950 on ns11.pliegergroep.it (89.20.180.74). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    refresh 1m is outside 20m–1d; retry 1m should be shorter than refresh 1m; expire 1m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1m must be longer than refresh + retry; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1m, retry 1m, expire 1m, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns11.pliegergroep.it is one of the listed nameservers.
  • ✓ Contact hostmaster@pliegergroep.it #25
    The SOA RNAME hostmaster.pliegergroep.it means hostmaster@pliegergroep.it.
  • ✓ Date-based serial #26
    The serial 2005120950 follows the YYYYMMDDnn convention (2005-12-09).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

17 records at the apex

Found

Read from
89.20.180.74:53
TypeValueTTL
SOAns11.pliegergroep.it. hostmaster.pliegergroep.it. 2005120950 60 60 60 6060
NSns11.pliegergroep.it.1
NSns12.pliegergroep.it.1
A13.94.170.3760
MX0 plieger-nl.mail.protection.outlook.com.300
TXT"google-site-verification=Nwj1ofK7JIp4UI_Fb45Iavy7Hp-A8hMmJbRiiRgZlk0"300
TXT"v=spf1 " "include:spf.protection.outlook.com " "include:amazonses.com " "ip4:89.20.180.68 " "ip4:89.20.180.79 " "include:_spf.relay.mailprotect.be " "include:europe.o365.crossware.co.nz " "-all"10
TXT""300
TXT"google-site-verification=lFA84BRUAxLJwx2zuZeL6d9mpH0bkSFfhTFMqxja30k"60
TXT"cisco-ci-domain-verification=2e91eaed95c605690b7ea4ae9b2b8f4f241141ec6df77546683b7bbbf5296058"300
TXT"globalsign-domain-verification=GN_W4dmbPl_8rhczFr-CApKFOciGnAbxoo2my7XC6Q"300
TXT"atlassian-sending-domain-verification=35acf461-d700-456a-9d43-943c65ea9433"300
TXT"anthropic-domain-verification-1jrhjx=b4c1J63Jfu623OuKTHsvNLDty"60
TXT"apple-domain-verification=lBQxFasnloGcUak1"300
TXT"wtcBZSMrCKd9u9Z9nbccpwfTfmZpJUhK8Z7ODlwKydc="300
TXT"google-site-verification=9Po5E9S9kwhbf31Voq-srCEYCIbNUgwWI2BOwndHw-0"300
TXT"atlassian-domain-verification=2hqT35tcEeqkAF/X8fyYazxF3ilsK1PPgZmhJRMLPa2BiAfhVrFH01Yw8jSVaecf"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), NS (1s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1s; 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