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

ns1.plongo.net, ns2.plongo.net

Nameserver	Addresses	Network (AS)	Glue
ns1.plongo.net	138.201.158.27 2a01:4f8:1c17:5d5b::1	AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE	-
ns2.plongo.net	138.201.95.30 2a01:4f8:1c17:6d9a::1	AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.plongo.net, ns2.plongo.net.

#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.
i

One address family in one network

all IPv6 addresses are in 2a01:4f8:1c17::/48, while the other address family is spread over several networks.

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 4 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 .net

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.

warn

4 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.plongo.net 138.201.158.27	NOERROR, 3 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17
ns1.plongo.net 2a01:4f8:1c17:5d5b::1	NOERROR, 6 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17
ns2.plongo.net 138.201.95.30	NOERROR, 3 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17
ns2.plongo.net 2a01:4f8:1c17:6d9a::1	NOERROR, 3 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17

✓ 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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.plongo.net: "PowerDNS Authoritative Server 4.9.17"; ns2.plongo.net: "PowerDNS Authoritative Server 4.9.17". 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.

pass

serial 2026030301 · primary ns1.plongo.net

✓ Serial 2026030301 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 ns1.plongo.net is one of the listed nameservers.
✓ Contact hostmaster@plongo.net #25

The SOA RNAME hostmaster.plongo.net means hostmaster@plongo.net.
✓ Date-based serial #26

The serial 2026030301 follows the YYYYMMDDnn convention (2026-03-03).

warn

Signed, but no DS at parent

!

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), RSASHA256 (8).
✓ Signatures valid until 2026-11-05 #30

The earliest DNSKEY/SOA signature expires at 2026-11-05 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

pass

15 records at the apex

Type	Value	TTL
SOA	ns1.plongo.net. hostmaster.plongo.net. 2026030301 43200 7200 1209600 600	7200
NS	ns2.plongo.net.	7200
NS	ns1.plongo.net.	7200
A	167.235.243.129	7200
AAAA	2a01:4f8:c012:ecf7::1	7200
MX	100 mail.plongo.net.	600
TXT	"v=spf1 ip4:148.251.180.209 ip6:2a01:4f8:211:753::2 ip4:94.130.129.217 ip6:2a01:4f8:13b:3a31::2 mx a ~all"	7200
TXT	"e0326f9e40b1754889fb49c29bde956252861ed6"	7200
TXT	"google-site-verification=R485QHFmv6i5ocmNOBusRpFerlMdVyqLaH-00tppQXg"	7200
CAA	0 issue "digicert.com"	7200
CAA	0 issuewild "letsencrypt.org"	7200
CAA	0 issuewild "sectigo.com"	7200
CAA	0 issuewild "digicert.com"	7200
CAA	0 issue "letsencrypt.org"	7200
CAA	0 issue "sectigo.com"	7200

✓ TTLs within range #32

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