aekwl.de

Checked 21 October 2026, 21:28 UTC · via 8.8.8.8
✗Problems found
20 passed 2 warnings 2 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

warn

pns.dtag.de, secondary004.dtag.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
pns.dtag.de, secondary004.dtag.net
NS in the zone
pns.dtag.de, secondary004.dtag.net, secondary006.dtag.net
NameserverAddressesNetwork (AS)Glue
pns.dtag.de194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.0.125 2003:40:8000::100
secondary004.dtag.net195.244.245.27 2a00:fa8:3:0:100:0:4:1AS5605 NETUSE - NetUSE AG, DE AS5605 NETUSE - NetUSE AG, DE-
secondary006.dtag.net (zone only)195.244.245.25 2a00:fa8:3:0:100:0:6:1AS5605 NETUSE - NetUSE AG, DE AS5605 NETUSE - NetUSE AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pns.dtag.de, secondary004.dtag.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: secondary006.dtag.net. pns.dtag.de, secondary004.dtag.net report NS pns.dtag.de secondary004.dtag.net secondary006.dtag.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 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS3320 (DTAG - Deutsche Telekom AG, DE): 2 addresses; AS5605 (NETUSE - NetUSE AG, DE): 4 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

4 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
pns.dtag.de 194.25.0.125NOERROR, 10 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100NOERROR, 8 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary004.dtag.net 195.244.245.27NOERROR, 12 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary004.dtag.net 2a00:fa8:3:0:100:0:4:1NOERROR, 17 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary006.dtag.net 195.244.245.25REFUSED, 13 ms, NOT authoritativenono / yesrefusedDomainNameServer
secondary006.dtag.net 2a00:fa8:3:0:100:0:6:1REFUSED, 17 ms, NOT authoritativenono / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 6 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: secondary006.dtag.net (195.244.245.25): REFUSED, authoritative=false; secondary006.dtag.net (2a00:fa8:3:0:100:0:6:1): REFUSED, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: pns.dtag.de: "DomainNameServer"; secondary004.dtag.net: "DomainNameServer"; secondary006.dtag.net: "DomainNameServer".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: secondary006.dtag.net (195.244.245.25): ; secondary006.dtag.net (2a00:fa8:3:0:100:0:6:1): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 2026100601 · primary dns.aekwl.de

Found

Primary (MNAME)
dns.aekwl.de
Contact (RNAME)
admin.aekwl.de
Serial
2026100601
Refresh / retry
21600 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
pns.dtag.de (194.25.0.125)2026100601
pns.dtag.de (2003:40:8000::100)2026100601
secondary004.dtag.net (195.244.245.27)2026100601
secondary004.dtag.net (2a00:fa8:3:0:100:0:4:1)2026100601

Checks

  • ✓ Serial 2026100601 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 2h, expire 14d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver dns.aekwl.de 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 admin@aekwl.de #25
    The SOA RNAME admin.aekwl.de means admin@aekwl.de.
  • ✓ Date-based serial #26
    The serial 2026100601 follows the YYYYMMDDnn convention (2026-10-06).

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

pass

16 records at the apex

Found

Read from
194.25.0.125:53
TypeValueTTL
SOAdns.aekwl.de. admin.aekwl.de. 2026100601 21600 7200 1209600 864002700
NSsecondary006.dtag.net.1800
NSpns.dtag.de.1800
NSsecondary004.dtag.net.1800
A62.159.20.1641800
MX10 mail.aekwl.de.1800
TXT"cisco-ci-domain-verification=7caf00fe60cc8f0c87e8a84368dc940fbef91988356df1c77860fafa34ebff32"1800
TXT"atlassian-domain-verification=fVdUtzrLNlBGucJIT4rmr2uOyjdw39QcFCeoT87aTPjzLyr6H7nQL3wOWXeQWDeB"1800
TXT"atlassian-sending-domain-verification=bb9706f3-8faf-4d54-af07-a2733fbeccfb"1800
TXT"v=spf1 include:_spf.jpberlin.de ip4:62.159.20.170 ip4:52.157.149.216 ip4:93.191.48.2 mx -all"1800
TXT"apple-domain-verification=4S1C44JyxYPv5JiN"1800
TXT"MS=8BB84D4EC4EE4242452336D8FAA70ACE3C4FB2CB"1800
TXT"25reports=588fdad15473b5b360c9c2a4"1800
CAA0 issue "letsencrypt.org"1800
CAA0 issue "telesec.de"1800
CAA0 issue "Digicert.com"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, MX 30m, NS 30m. The NS TTL at the parent is 1d and in the zone 30m; 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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, telesec.de, Digicert.com.