Domain report: imaginaerraum.de

Registration

info

.de country-code

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

info

ns0.0au.de, ns1.0au.de

Nameserver	Addresses	Network (AS)	Glue
ns0.0au.de	202.61.249.140 2a03:4000:54:dba::1	AS197540 netcup-AS - netcup GmbH, DE AS197540 netcup-AS - netcup GmbH, DE	202.61.249.140 2a03:4000:54:dba::1
ns1.0au.de	104.236.139.73 2604:a880:1:20::195:d001	AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US	104.236.139.73 2604:a880:1:20::195:d001

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns0.0au.de, ns1.0au.de.

#6
✓ 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 2 IPv4 /24s and 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses.
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.

pass

4 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns0.0au.de 202.61.249.140	NOERROR, 0 ms, authoritative	no	yes / yes	refused	-
ns0.0au.de 2a03:4000:54:dba::1	NOERROR, 1 ms, authoritative	no	yes / yes	refused	-
ns1.0au.de 104.236.139.73	NOERROR, 162 ms, authoritative	no	yes / yes	refused	-
ns1.0au.de 2604:a880:1:20::195:d001	NOERROR, 150 ms, authoritative	no	yes / yes	refused	-

✓ All respond #14

All 4 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.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ 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.

pass

serial 2023059246 · primary ns0.0au.de

✓ Serial 2023059246 everywhere #22

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

SOA refresh 3h, retry 30m, expire 7d, negative TTL 2h.
✓ Primary is a public nameserver #24

The primary nameserver ns0.0au.de is one of the listed nameservers.
✓ Contact apo2k4@gmail.com #25

The SOA RNAME apo2k4.gmail.com means apo2k4@gmail.com.
✓ Timestamp serial #26

The serial 2023059246 is a Unix timestamp (2034-02-09 00:54 UTC).

warn

Signed, but no DS at parent

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

!

Signed but not delegated securely

The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

#27
✓ Modern algorithms #29

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

The earliest DNSKEY/SOA signature expires at 2026-11-02 07:34 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

info

7 records at the apex