Domain report: geekheim.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

warn

first-dns.de, second-dns.de, third-dns.de

Nameserver	Addresses	Network (AS)	Glue
first-dns.de	194.150.168.53	AS250 SACREDCHAO-AS - IDDQD-AS, EU	-
second-dns.de	193.227.234.53	AS250 SACREDCHAO-AS - IDDQD-AS, EU	-
third-dns.de	193.227.234.52	AS250 SACREDCHAO-AS - IDDQD-AS, EU	-

✓ 3 nameservers #6

Delegated to first-dns.de, second-dns.de, third-dns.de.
✓ 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 0 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS250 (SACREDCHAO-AS - IDDQD-AS, EU): 3 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 .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
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

pass

3 of 3 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
first-dns.de 194.150.168.53	NOERROR, 3 ms, authoritative	no	yes / yes	refused	-
second-dns.de 193.227.234.53	NOERROR, 3 ms, authoritative	no	yes / yes	refused	-
third-dns.de 193.227.234.52	NOERROR, 3 ms, authoritative	no	yes / yes	refused	-

✓ All respond #14

All 3 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 2020060402 · primary first-dns.de

✓ Serial 2020060402 everywhere #22

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

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

The primary nameserver first-dns.de is one of the listed nameservers.
✓ Contact hostmaster@first-dns.de #25

The SOA RNAME hostmaster.first-dns.de means hostmaster@first-dns.de.
✓ Date-based serial #26

The serial 2020060402 follows the YYYYMMDDnn convention (2020-06-04).

warn

Not signed

info

6 records at the apex

Type	Value	TTL
SOA	first-dns.de. hostmaster.first-dns.de. 2020060402 10800 3600 604800 3600	3600
NS	first-dns.de.	3600
NS	third-dns.de.	3600
NS	second-dns.de.	3600
A	82.94.215.28	3600
MX	10 mail.svenfoo.org.	3600

✓ TTLs within range #32

TTLs: A 1h, MX 1h, 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.
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