jpberlin.de

Checked 21 October 2026, 23:01 UTC · via 8.8.8.8
!Passed with warnings
28 passed 3 warnings 0 failed 2 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

dns4.cloudns.net, dns7.cloudns.net, 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
dns4.cloudns.net, dns7.cloudns.net, ns.jpberlin.de, ns2.jpberlin.de, ns3.jpberlin.de
NS in the zone
dns4.cloudns.net, dns7.cloudns.net, ns.jpberlin.de, ns2.jpberlin.de, ns3.jpberlin.de
NameserverAddressesNetwork (AS)Glue
dns4.cloudns.net185.136.97.88 2a06:fb00:1::2:88AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
dns7.cloudns.net185.136.98.88 2a06:fb00:1::3:88AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
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

  • ✓ 5 nameservers #6
    Delegated to dns4.cloudns.net, dns7.cloudns.net, 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 5 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 5 autonomous systems #11
    The nameservers are spread over: AS199118 (HPLS-AS - Heinlein Support GmbH, DE): 2 addresses; AS203391 (CLOUDNSNET - Cloud DNS Ltd, BG): 4 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.
  • ✓ 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

warn

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns4.cloudns.net 185.136.97.88NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-3
dns4.cloudns.net 2a06:fb00:1::2:88NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-3
dns7.cloudns.net 185.136.98.88NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-3
dns7.cloudns.net 2a06:fb00:1::3:88NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-3
ns.jpberlin.de 91.198.250.3NOERROR, 10 ms, authoritativenoyes / yesrefused9.18.33
ns.jpberlin.de 2001:67c:2050:103:53:0:1:1NOERROR, 23 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, 1 ms, authoritativenoyes / yesrefused9.18.33
ns3.jpberlin.de 88.198.52.15NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.3.1
ns3.jpberlin.de 2a01:4f8:221:4381::1NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.3.1

Checks

  • ✓ All respond #14
    All 10 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 2014833027 · primary ns.jpberlin.de

Found

Primary (MNAME)
ns.jpberlin.de
Contact (RNAME)
root.jpberlin.de
Serial
2014833027
Refresh / retry
14400 s / 1800 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns4.cloudns.net (185.136.97.88)2014833027
dns4.cloudns.net (2a06:fb00:1::2:88)2014833027
dns7.cloudns.net (185.136.98.88)2014833027
dns7.cloudns.net (2a06:fb00:1::3:88)2014833027
ns.jpberlin.de (91.198.250.3)2014833027
ns.jpberlin.de (2001:67c:2050:103:53:0:1:1)2014833027
ns2.jpberlin.de (194.150.191.56)2014833027
ns2.jpberlin.de (2001:67c:14c:12f::56:2)2014833027
ns3.jpberlin.de (88.198.52.15)2014833027
ns3.jpberlin.de (2a01:4f8:221:4381::1)2014833027

Checks

  • ✓ Serial 2014833027 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, 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.
  • ✓ Timestamp serial #26
    The serial 2014833027 is a Unix timestamp (2033-11-05 19:50 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
100 iterations, 8-byte salt
Signatures valid until
12 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
18597RSASHA512 (10)SHA256 A4F0D91960A7C488…yes

DNSKEY in the zone

Key tagRoleAlgorithm
18597KSK (257)RSASHA512 (10)
32276ZSK (256)RSASHA512 (10)
8845ZSK (256)RSASHA512 (10)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 18597 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA512 (10).
  • ✓ Signatures valid until 2026-11-12 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-12 05:45 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 100 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

pass

18 records at the apex

Found

Read from
185.136.97.88:53
TypeValueTTL
SOAns.jpberlin.de. root.jpberlin.de. 2014833027 14400 1800 604800 864001800
NSns.jpberlin.de.300
NSdns7.cloudns.net.300
NSdns4.cloudns.net.300
NSns2.jpberlin.de.300
NSns3.jpberlin.de.300
A185.97.174.973600
MX50 mx-n.jpberlin.de.3600
MX10 mx2.jpberlin.de.3600
MX20 mx3.jpberlin.de.3600
MX10 mx1.jpberlin.de.3600
TXT"have-i-been-pwned-verification=5363f14ab484eda7d5bb6ddcdadb0295"300
TXT"v=spf1 mx include:_spf.jpberlin.de ~all"300
TXT"google-site-verification=rKtyr1-BDhpns_b3f5CHCYam9sRahVCNUenzY-XMwmc"300
CAA0 iodef "mailto:mail@heinlein-support.de"300
CAA0 iodef "mailto:security@heinlein-support.de"300
CAA0 issue "letsencrypt.org"300
CAA0 issue "digicert.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; 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, digicert.com.