chip.de

Checked 21 October 2026, 22:06 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

a1-118.akam.net, a16-67.akam.net, a2-64.akam.net, a28-65.akam.net, a5-66.akam.net, a7-67.akam.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
a1-118.akam.net, a16-67.akam.net, a2-64.akam.net, a28-65.akam.net, a5-66.akam.net, a7-67.akam.net
NS in the zone
a1-118.akam.net, a16-67.akam.net, a2-64.akam.net, a28-65.akam.net, a5-66.akam.net, a7-67.akam.net
NameserverAddressesNetwork (AS)Glue
a1-118.akam.net193.108.91.118 2600:1401:2::76AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a16-67.akam.net23.211.132.67 2600:1406:1b::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a2-64.akam.net95.100.174.64 2600:1480:7000::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a28-65.akam.net95.100.173.65 2600:1480:d800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a5-66.akam.net95.100.168.66 2600:1480:b000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a7-67.akam.net23.61.199.67 2600:1406:32::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-118.akam.net, a16-67.akam.net, a2-64.akam.net, a28-65.akam.net, a5-66.akam.net, a7-67.akam.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 6 IPv4 /24s and 6 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-118.akam.net 193.108.91.118NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9
a1-118.akam.net 2600:1401:2::76NOERROR, 4 ms, authoritativenoyes / yesrefused41824.8
a16-67.akam.net 23.211.132.67NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a16-67.akam.net 2600:1406:1b::43NOERROR, 3 ms, authoritativenoyes / yesrefused48878.33
a2-64.akam.net 95.100.174.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
a2-64.akam.net 2600:1480:7000::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a28-65.akam.net 95.100.173.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a28-65.akam.net 2600:1480:d800::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
a5-66.akam.net 95.100.168.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
a5-66.akam.net 2600:1480:b000::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.7
a7-67.akam.net 23.61.199.67NOERROR, 4 ms, authoritativenoyes / yesrefused41824.5
a7-67.akam.net 2600:1406:32::43NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10

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: a1-118.akam.net: "41824.9"; a1-118.akam.net: "41824.8"; a16-67.akam.net: "48878.26"; a16-67.akam.net: "48878.33"; a2-64.akam.net: "48878.27"; a2-64.akam.net: "48878.26"; a28-65.akam.net: "48878.29"; a28-65.akam.net: "48878.27"; a5-66.akam.net: "41824.11"; a5-66.akam.net: "41824.7"; a7-67.akam.net: "41824.5"; a7-67.akam.net: "41824.10". 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 2017023173 · primary a1-118.akam.net

Found

Primary (MNAME)
a1-118.akam.net
Contact (RNAME)
betrieb\.extern.chip.de
Serial
2017023173
Refresh / retry
14400 s / 1800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
a1-118.akam.net (193.108.91.118)2017023173
a1-118.akam.net (2600:1401:2::76)2017023173
a16-67.akam.net (23.211.132.67)2017023173
a16-67.akam.net (2600:1406:1b::43)2017023173
a2-64.akam.net (95.100.174.64)2017023173
a2-64.akam.net (2600:1480:7000::40)2017023173
a28-65.akam.net (95.100.173.65)2017023173
a28-65.akam.net (2600:1480:d800::41)2017023173
a5-66.akam.net (95.100.168.66)2017023173
a5-66.akam.net (2600:1480:b000::42)2017023173
a7-67.akam.net (23.61.199.67)2017023173
a7-67.akam.net (2600:1406:32::43)2017023173

Checks

  • ✓ Serial 2017023173 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-118.akam.net is one of the listed nameservers.
  • ✓ Contact betrieb.extern@chip.de #25
    The SOA RNAME betrieb\.extern.chip.de means betrieb.extern@chip.de.
  • ✓ Timestamp serial #26
    The serial 2017023173 is a Unix timestamp (2033-12-01 04:12 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

16 records at the apex

Found

Read from
193.108.91.118:53
TypeValueTTL
SOAa1-118.akam.net. betrieb\.extern.chip.de. 2017023173 14400 1800 604800 3600300
NSa7-67.akam.net.86400
NSa28-65.akam.net.86400
NSa2-64.akam.net.86400
NSa1-118.akam.net.86400
NSa16-67.akam.net.86400
NSa5-66.akam.net.86400
A2.16.1.21120
A2.16.1.18720
AAAA2a02:26f0:2780:68::217:e34c20
AAAA2a02:26f0:2780:68::217:e35420
MX10 chip-de.mail.protection.outlook.com.3600
TXT"v=spf1 mx include:_spf.general.transactional-mail-a.com include:spf.protection.outlook.com ~all"3600
TXT"adobe-idp-site-verification=3dd87aeb46d139cf0d8b7c78e2f0a96b5ebd3ad07d8aef6921d997884b0baeb1"3600
TXT"atlassian-domain-verification=ADXdiaemzjJXv0Cxw8MbdL09b6EY1y3t3z4LrFR0l20l2wrMZeZeAywXtZSkrPv7"3600
TXT"MS=ms18971433"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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