tician.de

Checked 22 October 2026, 00:40 UTC · via 8.8.8.8
✗Problems found
18 passed 4 warnings 1 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

ns1.tiker.net, ns2.tiker.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.tiker.net, ns2.tiker.net
NS in the zone
ns1.tiker.net, ns2.he.net, ns3.he.net, ns4.he.net, ns5.he.net
NameserverAddressesNetwork (AS)Glue
ns1.tiker.net49.13.195.233 2a01:4f8:1c1b:7294::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.he.net (zone only)216.218.131.2 2001:470:200::2AS6939 HURRICANE - Hurricane Electric LLC, US AS6939 HURRICANE - Hurricane Electric LLC, US-
ns2.tiker.net (parent only)216.66.80.18 2001:470:500::2AS6939 HURRICANE - Hurricane Electric LLC, US AS6939 HURRICANE - Hurricane Electric LLC, US-
ns3.he.net (zone only)216.218.132.2 2001:470:300::2AS6939 HURRICANE - Hurricane Electric LLC, US AS6939 HURRICANE - Hurricane Electric LLC, US-
ns4.he.net (zone only)216.66.1.2 2001:470:400::2AS6939 HURRICANE - Hurricane Electric LLC, US AS6939 HURRICANE - Hurricane Electric LLC, US-
ns5.he.net (zone only)216.66.80.18 2001:470:500::2AS6939 HURRICANE - Hurricane Electric LLC, US AS6939 HURRICANE - Hurricane Electric LLC, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.tiker.net, ns2.tiker.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.tiker.net; only in the zone: ns2.he.net, ns3.he.net, ns4.he.net, ns5.he.net. ns1.tiker.net, ns2.he.net, ns2.tiker.net, ns3.he.net, ns4.he.net, ns5.he.net report NS ns1.tiker.net ns2.he.net ns3.he.net ns4.he.net ns5.he.net.
    #7
  • ✓ 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 5 IPv4 /24s and 5 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS6939 (HURRICANE - Hurricane Electric LLC, US): 10 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

fail

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.tiker.net 49.13.195.233NOERROR, 4 ms, authoritativenoyes / yesALLOWED (16 records)9.20.29-1-Debian
ns1.tiker.net 2a01:4f8:1c1b:7294::1NOERROR, 3 ms, authoritativenoyes / yesALLOWED (16 records)9.20.29-1-Debian
ns2.he.net 216.218.131.2NOERROR, 33 ms, authoritativenoyes / yesrefused-
ns2.he.net 2001:470:200::2NOERROR, 33 ms, authoritativenoyes / yesrefused-
ns2.tiker.net 216.66.80.18NOERROR, 31 ms, authoritativenoyes / yesrefused-
ns2.tiker.net 2001:470:500::2NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns3.he.net 216.218.132.2NOERROR, 30 ms, authoritativenoyes / yesrefused-
ns3.he.net 2001:470:300::2NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns4.he.net 216.66.1.2NOERROR, 33 ms, authoritativenoyes / yesrefused-
ns4.he.net 2001:470:400::2NOERROR, 33 ms, authoritativenoyes / yesrefused-
ns5.he.net 216.66.80.18NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns5.he.net 2001:470:500::2NOERROR, 31 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 12 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: ns1.tiker.net: "9.20.29-1-Debian". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.tiker.net (49.13.195.233): 16 records; ns1.tiker.net (2a01:4f8:1c1b:7294::1): 16 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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

warn

serial 2024070101 · primary ns1.tiker.net

Found

Primary (MNAME)
ns1.tiker.net
Contact (RNAME)
abuse.tician.de
Serial
2024070101
Refresh / retry
3600 s / 3600 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.tiker.net (49.13.195.233)2024070101
ns1.tiker.net (2a01:4f8:1c1b:7294::1)2024070101
ns2.he.net (216.218.131.2)2024070101
ns2.he.net (2001:470:200::2)2024070101
ns2.tiker.net (216.66.80.18)2024070101
ns2.tiker.net (2001:470:500::2)2024070101
ns3.he.net (216.218.132.2)2024070101
ns3.he.net (2001:470:300::2)2024070101
ns4.he.net (216.66.1.2)2024070101
ns4.he.net (2001:470:400::2)2024070101
ns5.he.net (216.66.80.18)2024070101
ns5.he.net (2001:470:500::2)2024070101

Checks

  • ✓ Serial 2024070101 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.tiker.net is one of the listed nameservers.
  • ✓ Contact abuse@tician.de #25
    The SOA RNAME abuse.tician.de means abuse@tician.de.
  • ✓ Date-based serial #26
    The serial 2024070101 follows the YYYYMMDDnn convention (2024-07-01).

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

10 records at the apex

Found

Read from
49.13.195.233:53
TypeValueTTL
SOAns1.tiker.net. abuse.tician.de. 2024070101 3600 3600 2419200 36003600
NSns1.tiker.net.3600
NSns5.he.net.3600
NSns4.he.net.3600
NSns2.he.net.3600
NSns3.he.net.3600
A49.13.195.2333600
AAAA2a01:4f8:1c1b:7294::13600
MX0 smtp.tiker.net.3600
TXT"v=spf1 a:tiker.net mx ~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.
  • 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