region-stuttgart.de

Checked 22 October 2026, 00:00 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 8 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

dns1.lf.net, dns2.lf.net, dns3.lf.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.lf.net, dns2.lf.net, dns3.lf.net
NS in the zone
dns1.lf.net, dns2.lf.net, dns3.lf.net
NameserverAddressesNetwork (AS)Glue
dns1.lf.net212.9.160.10 2001:14b0:0:1:212:9:160:10AS12374 LFNET-AS01 - LF.net Netzwerksysteme GmbH, DE AS12374 LFNET-AS01 - LF.net Netzwerksysteme GmbH, DE-
dns2.lf.net62.50.111.2AS12374 LFNET-AS01 - LF.net Netzwerksysteme GmbH, DE-
dns3.lf.net3.77.208.173AS16509 AMAZON-02 - Amazon.com, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.lf.net, dns2.lf.net, dns3.lf.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 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12374 (LFNET-AS01 - LF.net Netzwerksysteme GmbH, DE): 3 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 1 address.
  • 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: dns2.lf.net, dns3.lf.net.
    #13

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.lf.net 212.9.160.10NOERROR, 14 ms, authoritativenoyes / yesrefusednone
dns1.lf.net 2001:14b0:0:1:212:9:160:10NOERROR, 10 ms, authoritativenoyes / yesrefusednone
dns2.lf.net 62.50.111.2NOERROR, 7 ms, authoritativenoyes / yesrefusednull
dns3.lf.net 3.77.208.173NOERROR, 4 ms, authoritativenoyes / yesrefusednull

Checks

  • ✓ All respond #14
    All 4 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns1.lf.net: "none"; dns2.lf.net: "null"; dns3.lf.net: "null".
    #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

info

serial 2026101202 · primary ns.lf.net

Found

Primary (MNAME)
ns.lf.net
Contact (RNAME)
hostmaster.lf.net
Serial
2026101202
Refresh / retry
86400 s / 10800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.lf.net (212.9.160.10)2026101202
dns1.lf.net (2001:14b0:0:1:212:9:160:10)2026101202
dns2.lf.net (62.50.111.2)2026101202
dns3.lf.net (3.77.208.173)2026101202

Checks

  • ✓ Serial 2026101202 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 3h, expire 7d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver ns.lf.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@lf.net #25
    The SOA RNAME hostmaster.lf.net means hostmaster@lf.net.
  • ✓ Date-based serial #26
    The serial 2026101202 follows the YYYYMMDDnn convention (2026-10-12).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
11 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
28925KSK (257)ECDSAP256SHA256 (13)
20635ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-11 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-11 08:18 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

8 records at the apex

Found

Read from
212.9.160.10:53
TypeValueTTL
SOAns.LF.net. hostmaster.LF.net. 2026101202 86400 10800 604800 36003600
NSdns2.LF.net.3600
NSdns3.LF.net.3600
NSdns1.LF.net.3600
A188.40.220.253600
AAAA2a01:4f8:1061:15ce::23600
MX20 regionstuttgart-de01e.mail.protection.outlook.com.3600
TXT"v=spf1 a:extmail.region-stuttgart.de include:spf.mailjet.com include:spf.protection.outlook.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 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.
  • ✓ 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