selfhost.de

Checked 22 October 2026, 00:10 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 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

pri.selfhost.de, sec.selfhost.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
pri.selfhost.de, sec.selfhost.de
NS in the zone
pri.selfhost.de, sec.selfhost.de
NameserverAddressesNetwork (AS)Glue
pri.selfhost.de82.98.82.20AS12306 PLUSLINE - Plus.line AG, DE82.98.82.20
sec.selfhost.de185.26.156.9AS58010 UVENSYS - uvensys GmbH, DE185.26.156.9

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pri.selfhost.de, sec.selfhost.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: pri.selfhost.de, sec.selfhost.de.
  • ✓ 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: AS12306 (PLUSLINE - Plus.line AG, DE): 1 address; AS58010 (UVENSYS - uvensys GmbH, DE): 1 address.
  • 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
pri.selfhost.de 82.98.82.20NOERROR, 4 ms, authoritativenoyes / norefused-
sec.selfhost.de 185.26.156.9NOERROR, 5 ms, authoritativenoyes / norefused-

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.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: pri.selfhost.de (82.98.82.20), sec.selfhost.de (185.26.156.9).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1792627796 · primary pri.selfhost.de

Found

Primary (MNAME)
pri.selfhost.de
Contact (RNAME)
hostmaster.selfhost.de
Serial
1792627796
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
2560 s

Serial per nameserver

NameserverSerial
pri.selfhost.de (82.98.82.20)1792627796
sec.selfhost.de (185.26.156.9)1792627796

Checks

  • ✓ Serial 1792627796 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 42m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pri.selfhost.de is one of the listed nameservers.
  • ✓ Contact hostmaster@selfhost.de #25
    The SOA RNAME hostmaster.selfhost.de means hostmaster@selfhost.de.
  • ✓ Timestamp serial #26
    The serial 1792627796 is a Unix timestamp (2026-10-22 00:09 UTC).

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

warn

7 records at the apex

Found

Read from
82.98.82.20:53
TypeValueTTL
SOApri.selfhost.de. hostmaster.selfhost.de. 1792627796 16384 2048 1048576 25602560
NSpri.selfhost.de.345600
NSsec.selfhost.de.345600
A185.139.158.4460
MX10 kirk.selfhost.de.60
TXT"google-site-verification=87jgY4kPeRHHK5JpT8rQE8NQOulwrAX1eyVh0OmTylc"10
TXT"v=spf1 a:kepler.selfhost.de a:kirk.selfhost.de a:dilbert.selfhost.de a:smtpud01.udag.de a:smtpud02.udag.de ~all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 4d; resolvers may use either.
    #32
  • ✓ 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