ghwk.de

Checked 21 October 2026, 22:40 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 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

ns1.asok.de, ns2.asok.de, ns3.asok.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.asok.de, ns2.asok.de, ns3.asok.de
NS in the zone
ns1.asok.de, ns2.asok.de, ns3.asok.de
NameserverAddressesNetwork (AS)Glue
ns1.asok.de185.26.156.180 2a00:d0c0:200:0:b9:1a:9c:86AS58010 UVENSYS - uvensys GmbH, DE AS58010 UVENSYS - uvensys GmbH, DE-
ns2.asok.de95.143.172.180 2001:1a50:11:0:5f:8f:ac:b4AS25560 RHTEC-AS - rh-tec Business GmbH, DE AS25560 RHTEC-AS - rh-tec Business GmbH, DE-
ns3.asok.de82.98.82.180 2a02:2e0:3fc:52:0:62:52:b4AS12306 PLUSLINE - Plus.line AG, DE AS12306 PLUSLINE - Plus.line AG, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.asok.de, ns2.asok.de, ns3.asok.de.
  • ✓ 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.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS12306 (PLUSLINE - Plus.line AG, DE): 2 addresses; AS25560 (RHTEC-AS - rh-tec Business GmbH, DE): 2 addresses; AS58010 (UVENSYS - uvensys GmbH, DE): 2 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.asok.de 185.26.156.180NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.1
ns1.asok.de 2a00:d0c0:200:0:b9:1a:9c:86NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.1
ns2.asok.de 95.143.172.180NOERROR, 3 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.1
ns2.asok.de 2001:1a50:11:0:5f:8f:ac:b4NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.1
ns3.asok.de 82.98.82.180NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.1
ns3.asok.de 2a02:2e0:3fc:52:0:62:52:b4NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.1

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.asok.de: "Knot DNS 3.5.1"; ns2.asok.de: "Knot DNS 3.5.1"; ns3.asok.de: "Knot DNS 3.5.1". 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 1771332060 · primary ns1.asok.de

Found

Primary (MNAME)
ns1.asok.de
Contact (RNAME)
hostmaster.asok.de
Serial
1771332060
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.asok.de (185.26.156.180)1771332060
ns1.asok.de (2a00:d0c0:200:0:b9:1a:9c:86)1771332060
ns2.asok.de (95.143.172.180)1771332060
ns2.asok.de (2001:1a50:11:0:5f:8f:ac:b4)1771332060
ns3.asok.de (82.98.82.180)1771332060
ns3.asok.de (2a02:2e0:3fc:52:0:62:52:b4)1771332060

Checks

  • ✓ Serial 1771332060 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.asok.de is one of the listed nameservers.
  • ✓ Contact hostmaster@asok.de #25
    The SOA RNAME hostmaster.asok.de means hostmaster@asok.de.
  • ✓ Timestamp serial #26
    The serial 1771332060 is a Unix timestamp (2026-02-17 12:41 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

11 records at the apex

Found

Read from
185.26.156.180:53
TypeValueTTL
SOAns1.asok.de. hostmaster.asok.de. 1771332060 10800 3600 604800 36003600
NSns1.asok.de.3600
NSns2.asok.de.3600
NSns3.asok.de.3600
A88.198.166.6910
MX1 ghwk-de.mail.protection.outlook.com.3600
TXT"MS=ms51799711"10
TXT"MS=C6108E25C1DF910F1A6A83D77CD42D440C56E209"10
TXT"v=spf1 include:spf.protection.outlook.com ip4:193.96.188.0/24 -all"10
TXT"google-site-verification=GMw_NqhjWD5w0ENgmER5pRrOT0bQP4MHA9nAGlZ7ydw"10
TXT"_globalsign-domain-verification=p4VOjLSoque2dqEJN4SEhGFgKcl4IijhCt1HxToM_5"10

Checks

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