levensmiddelenkrant.nl

Checked 22 October 2026, 14:10 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1.elcanet.nl, ns2.elcanet.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.elcanet.nl, ns2.elcanet.nl
NS in the zone
ns1.elcanet.nl, ns2.elcanet.nl
NameserverAddressesNetwork (AS)Glue
ns1.elcanet.nl83.98.164.11AS49127 ASIMO-AS - Asimo Networks B.V., NL83.98.164.11
ns2.elcanet.nl136.144.181.218AS20857 TRANSIP-AS - Signet B.V., NL136.144.181.218

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.elcanet.nl, ns2.elcanet.nl.
    #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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20857 (TRANSIP-AS - Signet B.V., NL): 1 address; AS49127 (ASIMO-AS - Asimo Networks B.V., NL): 1 address.
  • i
    All nameserver names under .nl
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.elcanet.nl 83.98.164.11NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.elcanet.nl 136.144.181.218NOERROR, 11 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

pass

serial 2024071208 · primary ns1.elcanet.nl

Found

Primary (MNAME)
ns1.elcanet.nl
Contact (RNAME)
hostmaster.elcanet.nl
Serial
2024071208
Refresh / retry
28800 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.elcanet.nl (83.98.164.11)2024071208
ns2.elcanet.nl (136.144.181.218)2024071208

Checks

  • ✓ Serial 2024071208 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.elcanet.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@elcanet.nl #25
    The SOA RNAME hostmaster.elcanet.nl means hostmaster@elcanet.nl.
  • ✓ Date-based serial #26
    The serial 2024071208 follows the YYYYMMDDnn convention (2024-07-12).

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

info

8 records at the apex

Found

Read from
83.98.164.11:53
TypeValueTTL
SOAns1.elcanet.nl. hostmaster.elcanet.nl. 2024071208 28800 7200 1209600 8640086400
NSns2.elcanet.nl.86400
NSns1.elcanet.nl.86400
A85.10.138.2163600
AAAA2a01:7c8:bb0b:587:5054:ff:feac:83e93600
MX0 levensmiddelenkrant-nl.mail.protection.outlook.com.600
TXT"v=spf1 a mx ip4:83.98.164.0/24 ip4:195.201.31.243 ip4:5.200.25.65/27 include:spf.protection.outlook.com ~all"600
TXT"MS=ms15543390"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 10m, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ 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