attac.de

Checked 21 October 2026, 21:31 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 4 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

ns.jpberlin.de, ns2.jpberlin.de, ns3.jpberlin.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.jpberlin.de, ns2.jpberlin.de, ns3.jpberlin.de
NS in the zone
ns.jpberlin.de, ns2.jpberlin.de, ns3.jpberlin.de
NameserverAddressesNetwork (AS)Glue
ns.jpberlin.de91.198.250.3 2001:67c:2050:103:53:0:1:1AS199118 HPLS-AS - Heinlein Support GmbH, DE AS199118 HPLS-AS - Heinlein Support GmbH, DE91.198.250.3 2001:67c:2050:1::53:1
ns2.jpberlin.de194.150.191.56 2001:67c:14c:12f::56:2AS62313 PROACT-AS - Proact IT UK Limited, GB AS33988 PROACTDE - Proact Deutschland GmbH, DE194.150.191.56 2001:67c:14c:12f::56:2
ns3.jpberlin.de88.198.52.15 2a01:4f8:221:4381::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE88.198.52.15

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.jpberlin.de, ns2.jpberlin.de, ns3.jpberlin.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns.jpberlin.de (glue 91.198.250.3, 2001:67c:2050:1::53:1, zone 91.198.250.3, 2001:67c:2050:103:53:0:1:1); ns3.jpberlin.de (glue 88.198.52.15, zone 88.198.52.15, 2a01:4f8:221:4381::1). Update the glue at your registrar.
    #8
  • ✓ 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.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS199118 (HPLS-AS - Heinlein Support GmbH, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS33988 (PROACTDE - Proact Deutschland GmbH, DE): 1 address; AS62313 (PROACT-AS - Proact IT UK Limited, GB): 1 address.
  • 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
ns.jpberlin.de 91.198.250.3NOERROR, 10 ms, authoritativenoyes / yesrefused9.18.33
ns.jpberlin.de 2001:67c:2050:103:53:0:1:1NOERROR, 24 ms, authoritativenoyes / yesrefused9.18.33
ns2.jpberlin.de 194.150.191.56NOERROR, 0 ms, authoritativenoyes / yesrefused9.18.33
ns2.jpberlin.de 2001:67c:14c:12f::56:2NOERROR, 0 ms, authoritativenoyes / yesrefused9.18.33
ns3.jpberlin.de 88.198.52.15NOERROR, 2 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.3.1
ns3.jpberlin.de 2a01:4f8:221:4381::1NOERROR, 2 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.3.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: ns.jpberlin.de: "9.18.33"; ns2.jpberlin.de: "9.18.33"; ns3.jpberlin.de: "PowerDNS Authoritative Server 4.3.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 2026101901 · primary ns.jpberlin.de

Found

Primary (MNAME)
ns.jpberlin.de
Contact (RNAME)
root.jpberlin.de
Serial
2026101901
Refresh / retry
40000 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.jpberlin.de (91.198.250.3)2026101901
ns.jpberlin.de (2001:67c:2050:103:53:0:1:1)2026101901
ns2.jpberlin.de (194.150.191.56)2026101901
ns2.jpberlin.de (2001:67c:14c:12f::56:2)2026101901
ns3.jpberlin.de (88.198.52.15)2026101901
ns3.jpberlin.de (2a01:4f8:221:4381::1)2026101901

Checks

  • ✓ Serial 2026101901 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 11h6m40s, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.jpberlin.de is one of the listed nameservers.
  • ✓ Contact root@jpberlin.de #25
    The SOA RNAME root.jpberlin.de means root@jpberlin.de.
  • ✓ Date-based serial #26
    The serial 2026101901 follows the YYYYMMDDnn convention (2026-10-19).

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

9 records at the apex

Found

Read from
91.198.250.3:53
TypeValueTTL
SOAns.jpberlin.de. root.jpberlin.de. 2026101901 40000 7200 604800 8640060
NSns3.jpberlin.de.60
NSns2.jpberlin.de.60
NSns.jpberlin.de.60
A80.241.60.16960
MX20 mx3.heinlein-support.de.60
MX10 mx2.heinlein-support.de.60
MX10 mx1.heinlein-support.de.60
TXT"v=spf1 mx include:_spf.jpberlin.de ?all"60

Checks

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