rothaus.de

Checked 22 October 2026, 00:01 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

ext-ns.lf.net, ns1.pcom.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ext-ns.lf.net, ns1.pcom.de
NS in the zone
ext-ns.lf.net, ns1.pcom.de
NameserverAddressesNetwork (AS)Glue
ext-ns.lf.net212.9.161.77AS12374 LFNET-AS01 - LF.net Netzwerksysteme GmbH, DE-
ns1.pcom.de194.25.152.2 2003:de:c017:1001::1:1AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.152.2 2003:de:c017:1001::1:1

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ext-ns.lf.net, ns1.pcom.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 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12374 (LFNET-AS01 - LF.net Netzwerksysteme GmbH, DE): 1 address; AS3320 (DTAG - Deutsche Telekom AG, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ext-ns.lf.net.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ext-ns.lf.net 212.9.161.77NOERROR, 7 ms, authoritativenoyes / yesrefused9.7.3
ns1.pcom.de 194.25.152.2NOERROR, 13 ms, authoritativenoyes / yesrefusedN.N.
ns1.pcom.de 2003:de:c017:1001::1:1NOERROR, 14 ms, authoritativenoyes / yesrefusedN.N.

Checks

  • ✓ All respond #14
    All 3 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: ext-ns.lf.net: "9.7.3". 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 2026031201 · primary ns1.pcom.de

Found

Primary (MNAME)
ns1.pcom.de
Contact (RNAME)
admin.pcom.de
Serial
2026031201
Refresh / retry
86400 s / 7200 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ext-ns.lf.net (212.9.161.77)2026031201
ns1.pcom.de (194.25.152.2)2026031201
ns1.pcom.de (2003:de:c017:1001::1:1)2026031201

Checks

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

9 records at the apex

Found

Read from
212.9.161.77:53
TypeValueTTL
SOAns1.pcom.de. admin.pcom.de. 2026031201 86400 7200 1209600 36003600
NSns1.pcom.de.3600
NSext-ns.LF.net.3600
A88.198.176.2443600
MX10 rothaus-de.mail.protection.outlook.com.3600
TXT"apple-domain-verification=eBYm4hGp9D12ppzg"3600
TXT"atlassian-domain-verification=71quXw3JoH4u0f1egnylayLD6ePqUDRyxTN72lruf61xB/rj4WVKmYwyqaMvoaBQ"3600
TXT"v=spf1 a mx include:spf.protection.outlook.com ip4:80.149.147.131 ip4:87.193.142.100 ip4:136.243.162.142 -all"3600
TXT"MS=ms39003045"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.
  • ✓ 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