ln-online.de

Checked 21 October 2026, 23:20 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 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

info

ns0.niedersachsen.com, pns.dtag.de, secondary006.dtag.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns0.niedersachsen.com, pns.dtag.de, secondary006.dtag.net
NS in the zone
ns0.niedersachsen.com, pns.dtag.de, secondary006.dtag.net
NameserverAddressesNetwork (AS)Glue
ns0.niedersachsen.com193.30.60.250AS3209 VODANET - Vodafone GmbH, DE-
pns.dtag.de194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.0.125 2003:40:8000::100
secondary006.dtag.net195.244.245.25 2a00:fa8:3:0:100:0:6:1AS5605 NETUSE - NetUSE AG, DE AS5605 NETUSE - NetUSE AG, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns0.niedersachsen.com, pns.dtag.de, secondary006.dtag.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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS3209 (VODANET - Vodafone GmbH, DE): 1 address; AS3320 (DTAG - Deutsche Telekom AG, DE): 2 addresses; AS5605 (NETUSE - NetUSE AG, DE): 2 addresses.
  • ✓ Nameserver names under 3 TLDs #12
    Nameserver names use the TLDs .com, .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns0.niedersachsen.com.
    #13

Nameservers

warn

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.niedersachsen.com 193.30.60.250NOERROR, 11 ms, authoritativenoyes / yesrefused9.20.29
pns.dtag.de 194.25.0.125NOERROR, 10 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100NOERROR, 7 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary006.dtag.net 195.244.245.25NOERROR, 14 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary006.dtag.net 2a00:fa8:3:0:100:0:6:1NOERROR, 18 ms, authoritativenoyes / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 5 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: ns0.niedersachsen.com: "9.20.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

pass

serial 2026100725 · primary ns0.niedersachsen.com

Found

Primary (MNAME)
ns0.niedersachsen.com
Contact (RNAME)
dns.gutenberg-rz.de
Serial
2026100725
Refresh / retry
14400 s / 3600 s
Expire
1814400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns0.niedersachsen.com (193.30.60.250)2026100725
pns.dtag.de (194.25.0.125)2026100725
pns.dtag.de (2003:40:8000::100)2026100725
secondary006.dtag.net (195.244.245.25)2026100725
secondary006.dtag.net (2a00:fa8:3:0:100:0:6:1)2026100725

Checks

  • ✓ Serial 2026100725 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 21d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.niedersachsen.com is one of the listed nameservers.
  • ✓ Contact dns@gutenberg-rz.de #25
    The SOA RNAME dns.gutenberg-rz.de means dns@gutenberg-rz.de.
  • ✓ Date-based serial #26
    The serial 2026100725 follows the YYYYMMDDnn convention (2026-10-07).

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
193.30.60.250:53
TypeValueTTL
SOAns0.niedersachsen.com. dns.gutenberg-rz.de. 2026100725 14400 3600 1814400 36003600
NSsecondary006.dtag.net.3600
NSpns.dtag.de.3600
NSns0.niedersachsen.com.3600
A193.30.60.2453600
MX10 lnonline-de0e.mail.protection.outlook.com.3600
TXT"v=spf1 include:spf.protection.outlook.com include:spf.pushwoosh.io include:spf.gutenberg-rz.de include:amazonses.com ~all"3600
TXT"amazonses:XdDHFMegl9PbsVHgn7P2nv5fNDY0ZgjOYOLc3ITKs2o="3600
TXT"0bR/nm7+nqPwvq38jFGDaIlIXrLFOZULKnc0Wh9yeryaKoZ+IV3oirzx6FBgk/n9ADYxOSZbgjsjcseYEatFEA=="3600
TXT"MS=ms51310607"3600
TXT"google-site-verification=30O-9xG8U4OjepGl9R2_6UM9VogkvXILNCEGaTDXtp4"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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