zettelkasten.de

Checked 22 October 2026, 01:20 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 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

info

dns1.hostsharing.net, dns2.hostsharing.net, dns3.hostsharing.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.hostsharing.net, dns2.hostsharing.net, dns3.hostsharing.net
NS in the zone
dns1.hostsharing.net, dns2.hostsharing.net, dns3.hostsharing.net
NameserverAddressesNetwork (AS)Glue
dns1.hostsharing.net83.223.95.201 2a01:37:1000::53df:5fc9:0AS8875 SINMA-ASN - sinma GmbH, DE AS8875 SINMA-ASN - sinma GmbH, DE-
dns2.hostsharing.net83.223.78.230 2a01:37:3000::53df:4ee6:0AS8875 SINMA-ASN - sinma GmbH, DE AS8875 SINMA-ASN - sinma GmbH, DE-
dns3.hostsharing.net144.76.133.101 2a01:4f8:fff3:b8::101AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.hostsharing.net, dns2.hostsharing.net, dns3.hostsharing.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 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS8875 (SINMA-ASN - sinma GmbH, DE): 4 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.hostsharing.net 83.223.95.201NOERROR, 9 ms, authoritativenoyes / yesrefused-
dns1.hostsharing.net 2a01:37:1000::53df:5fc9:0NOERROR, 11 ms, authoritativenoyes / yesrefused-
dns2.hostsharing.net 83.223.78.230NOERROR, 8 ms, authoritativenoyes / yesrefused-
dns2.hostsharing.net 2a01:37:3000::53df:4ee6:0NOERROR, 11 ms, authoritativenoyes / yesrefused-
dns3.hostsharing.net 144.76.133.101NOERROR, 2 ms, authoritativenoyes / yesrefused-
dns3.hostsharing.net 2a01:4f8:fff3:b8::101NOERROR, 2 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 1734113964 · primary h42.hostsharing.net

Found

Primary (MNAME)
h42.hostsharing.net
Contact (RNAME)
hostmaster.hostsharing.net
Serial
1734113964
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.hostsharing.net (83.223.95.201)1734113964
dns1.hostsharing.net (2a01:37:1000::53df:5fc9:0)1734113964
dns2.hostsharing.net (83.223.78.230)1734113964
dns2.hostsharing.net (2a01:37:3000::53df:4ee6:0)1734113964
dns3.hostsharing.net (144.76.133.101)1734113964
dns3.hostsharing.net (2a01:4f8:fff3:b8::101)1734113964

Checks

  • ✓ Serial 1734113964 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver h42.hostsharing.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@hostsharing.net #25
    The SOA RNAME hostmaster.hostsharing.net means hostmaster@hostsharing.net.
  • ✓ Timestamp serial #26
    The serial 1734113964 is a Unix timestamp (2024-12-13 18:19 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

info

11 records at the apex

Found

Read from
83.223.95.201:53
TypeValueTTL
SOAh42.hostsharing.net. hostmaster.hostsharing.net. 1734113964 21600 3600 604800 360021600
NSdns2.hostsharing.net.21600
NSdns1.hostsharing.net.21600
NSdns3.hostsharing.net.21600
A83.223.95.1221600
AAAA2a01:37:1000::53df:5f0c:021600
MX30 mailin3.hostsharing.net.21600
MX30 mailin2.hostsharing.net.21600
MX30 mailin1.hostsharing.net.21600
TXT"v=spf1 include:spf.hostsharing.net -all"21600
TXT"google-site-verification=Y9FYMSHqxwU_WXTKGY-USF6AFI7z9O2TfN-DtatFBEs"21600

Checks

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