Domain report: openjur.de

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

pass

ns1.openjur.net, ns2.oj.is, ns3.openjur.de

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: ns1.openjur.net, ns2.oj.is, ns3.openjur.de
NS in the zone: ns1.openjur.net, ns2.oj.is, ns3.openjur.de

Nameserver	Addresses	Network (AS)	Glue
ns1.openjur.net	2.58.53.227 2a0c:8900:5::add6:42f3	AS200462 AS-ETH - Lennart Seitz trading as _ETH-Services_, DE AS200462 AS-ETH - Lennart Seitz trading as _ETH-Services_, DE	-
ns2.oj.is	213.160.75.155 2a00:17d8:100::38a1	AS12574 ROUTING - Hosting.de GmbH, DE AS12574 ROUTING - Hosting.de GmbH, DE	-
ns3.openjur.de	162.55.175.229 2a01:4f8:c013:f31b::1	AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE	162.55.175.229 2a01:4f8:c013:f31b::1

Checks

✓ 3 nameservers #6

Delegated to ns1.openjur.net, ns2.oj.is, ns3.openjur.de.
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ Glue present and correct #8

Glue is published for the nameservers inside the zone: ns3.openjur.de.
✓ 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: AS12574 (ROUTING - Hosting.de GmbH, DE): 2 addresses; AS200462 (AS-ETH - Lennart Seitz trading as _ETH-Services_, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses.
✓ Nameserver names under 3 TLDs #12

Nameserver names use the TLDs .de, .is, .net.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

fail

5 of 6 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.openjur.net 2.58.53.227	NOERROR, 8 ms, authoritative	no	yes / yes	refused	fra1
ns1.openjur.net 2a0c:8900:5::add6:42f3	NOERROR, 7 ms, authoritative	no	yes / yes	refused	fra1
ns2.oj.is 213.160.75.155	NOERROR, 13 ms, authoritative	no	yes / yes	refused	ac1
ns2.oj.is 2a00:17d8:100::38a1	NOERROR, 9 ms, authoritative	no	yes / yes	refused	ac1
ns3.openjur.de 162.55.175.229	NOERROR, 8 ms, authoritative	no	yes / yes	refused	fsn1
ns3.openjur.de 2a01:4f8:c013:f31b::1	no response	no	no / no	-	-

Checks

✗

Nameservers not responding

These addresses did not answer, so resolvers waste time on timeouts: ns3.openjur.de (2a01:4f8:c013:f31b::1): read udp [2a01:4f8:1c1c:eebf::1]:37978->[2a01:4f8:c013:f31b::1]:53: i/o timeout.

#14
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ 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: ns1.openjur.net: "fra1"; ns2.oj.is: "ac1"; ns3.openjur.de: "fsn1".

#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 2026060200 · primary ns3.openjur.de

Found

Primary (MNAME): ns3.openjur.de
Contact (RNAME): domains.openjur.de
Serial: 2026060200
Refresh / retry: 43200 s / 7200 s
Expire: 1209600 s
Negative TTL: 600 s

Serial per nameserver

Nameserver	Serial
ns1.openjur.net (2.58.53.227)	2026060200
ns1.openjur.net (2a0c:8900:5::add6:42f3)	2026060200
ns2.oj.is (213.160.75.155)	2026060200
ns2.oj.is (2a00:17d8:100::38a1)	2026060200
ns3.openjur.de (162.55.175.229)	2026060200

Checks

✓ Serial 2026060200 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 12h, retry 2h, expire 14d, negative TTL 10m.
✓ Primary is a public nameserver #24

The primary nameserver ns3.openjur.de is one of the listed nameservers.
✓ Contact domains@openjur.de #25

The SOA RNAME domains.openjur.de means domains@openjur.de.
✓ Date-based serial #26

The serial 2026060200 follows the YYYYMMDDnn convention (2026-06-02).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC
Signatures valid until: 29 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
4420	ECDSAP256SHA256 (13)	SHA256 13A840DC6C7C4021…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
4420	KSK (257)	ECDSAP256SHA256 (13)

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 4420 (SHA256).
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13).
✓ Signatures valid until 2026-10-29 #30

The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
i

NSEC

The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

#31

Records

pass

11 records at the apex

Found

Read from: 2.58.53.227:53

Type	Value	TTL
SOA	ns3.openjur.de. domains.openjur.de. 2026060200 43200 7200 1209600 600	3600
NS	ns2.oj.is.	3600
NS	ns1.openjur.net.	3600
NS	ns3.openjur.de.	3600
A	212.12.52.193	600
AAAA	2a00:14b0:4200:3400:193::1	600
MX	10 mail-in.openjur.net.	600
TXT	"google-site-verification=O48-RD0NkrBjew7rY7N-MwtwvheIHt8QTKSXD9LApp0"	600
TXT	"v=spf1 mx a:mail-out.openjur.net -all"	600
CAA	0 issue "digicert.com"	600
CAA	0 issue "letsencrypt.org"	600

Checks

✓ TTLs within range #32

TTLs: A 10m, AAAA 10m, MX 10m, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; 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: digicert.com, letsencrypt.org.