lueneburg.de

Checked 21 October 2026, 23:20 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 warnings 0 failed 6 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de 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
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

warn

dns01.luenecom.de, dns02.luenecom.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns01.luenecom.de, dns02.luenecom.de
NS in the zone
dns01.luenecom.de, dns02.luenecom.de
NameserverAddressesNetwork (AS)Glue
dns01.luenecom.de213.252.154.2AS9066 BCC - EWE TEL GmbH, DE213.252.154.2
dns02.luenecom.de213.252.158.2AS9066 BCC - EWE TEL GmbH, DE213.252.158.2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns01.luenecom.de, dns02.luenecom.de.
    #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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS9066 (BCC - EWE TEL GmbH, DE): 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 .de
    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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns01.luenecom.de 213.252.154.2NOERROR, 20 ms, authoritativenoyes / yesrefused9.16.50-Debian
dns02.luenecom.de 213.252.158.2NOERROR, 15 ms, authoritativenoyes / yesrefused9.16.50-Debian

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns01.luenecom.de: "9.16.50-Debian"; dns02.luenecom.de: "9.16.50-Debian". 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 2026060961 · primary dns01.luenecom.de

Found

Primary (MNAME)
dns01.luenecom.de
Contact (RNAME)
info.dns01.luenecom.de
Serial
2026060961
Refresh / retry
21600 s / 3600 s
Expire
1814400 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
dns01.luenecom.de (213.252.154.2)2026060961
dns02.luenecom.de (213.252.158.2)2026060961

Checks

  • ✓ Serial 2026060961 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 21d, negative TTL 12h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns01.luenecom.de is one of the listed nameservers.
  • ✓ Contact info@dns01.luenecom.de #25
    The SOA RNAME info.dns01.luenecom.de means info@dns01.luenecom.de.
  • ✓ Date-based serial #26
    The serial 2026060961 follows the YYYYMMDDnn convention (2026-06-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

info

11 records at the apex

Found

Read from
213.252.154.2:53
TypeValueTTL
SOAdns01.luenecom.de. info.dns01.luenecom.de. 2026060961 21600 3600 1814400 4320043200
NSdns01.luenecom.de.43200
NSdns02.luenecom.de.43200
A5.159.58.20643200
A5.159.62.24443200
AAAA2a04:79c0:0:401::443200
AAAA2a04:79c0:1010:5002::643200
MX5 mail05.luenecom.de.43200
TXT"28f30f14c14df6994cadc35762f977760b738503c8bfdf04cfb32ba90a7026d"43200
TXT"v=spf1 mx ~all"43200
TXT"53697c6e19e2fc1f15c93c906468ab01fa4a4c1cbe3cb6ef7568d027534e01f"43200

Checks

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