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

info

ns1.mcs.de, ns2.mcs.de, ns3.mcs.de

Found

Parent zone: gov.de
Delegation from: ns1-any.123ns.eu (195.253.64.5)
NS at the parent: ns1.mcs.de, ns2.mcs.de, ns3.mcs.de
NS in the zone: ns1.mcs.de, ns2.mcs.de, ns3.mcs.de

Nameserver	Addresses	Network (AS)	Glue
ns1.mcs.de	147.78.89.212 2a09:2040:0:16::10	AS215992 MCS-AS - MCS GmbH, DE AS215992 MCS-AS - MCS GmbH, DE	-
ns2.mcs.de	147.78.89.220 2a09:2040:0:17::10	AS215992 MCS-AS - MCS GmbH, DE AS215992 MCS-AS - MCS GmbH, DE	-
ns3.mcs.de	194.13.83.222 2a03:4000:43:502::1	AS197540 netcup-AS - netcup GmbH, DE AS197540 netcup-AS - netcup GmbH, DE	-

Checks

✓ 3 nameservers #6

Delegated to ns1.mcs.de, ns2.mcs.de, ns3.mcs.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 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses; AS215992 (MCS-AS - MCS GmbH, DE): 4 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.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.mcs.de 147.78.89.212	NOERROR, 12 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.8.3
ns1.mcs.de 2a09:2040:0:16::10	NOERROR, 12 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.8.3
ns2.mcs.de 147.78.89.220	NOERROR, 12 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.8.3
ns2.mcs.de 2a09:2040:0:17::10	NOERROR, 12 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.8.3
ns3.mcs.de 194.13.83.222	NOERROR, 1 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.8.3
ns3.mcs.de 2a03:4000:43:502::1	NOERROR, 1 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.8.3

Checks

✓ All respond #14

All 6 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.mcs.de: "PowerDNS Authoritative Server 4.8.3"; ns2.mcs.de: "PowerDNS Authoritative Server 4.8.3"; ns3.mcs.de: "PowerDNS Authoritative Server 4.8.3". 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 2026091400 · primary ns1.mcs.de

Found

Primary (MNAME): ns1.mcs.de
Contact (RNAME): hostmaster.mcs.de
Serial: 2026091400
Refresh / retry: 14400 s / 3600 s
Expire: 604800 s
Negative TTL: 600 s

Serial per nameserver

Nameserver	Serial
ns1.mcs.de (147.78.89.212)	2026091400
ns1.mcs.de (2a09:2040:0:16::10)	2026091400
ns2.mcs.de (147.78.89.220)	2026091400
ns2.mcs.de (2a09:2040:0:17::10)	2026091400
ns3.mcs.de (194.13.83.222)	2026091400
ns3.mcs.de (2a03:4000:43:502::1)	2026091400

Checks

✓ Serial 2026091400 everywhere #22

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

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

The primary nameserver ns1.mcs.de is one of the listed nameservers.
✓ Contact hostmaster@mcs.de #25

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

The serial 2026091400 follows the YYYYMMDDnn convention (2026-09-14).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC
Signatures valid until: 5 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
7909	RSASHA256 (8)	SHA256 03559C63B322D626…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
29808	ZSK (256)	RSASHA256 (8)
7909	KSK (257)	RSASHA256 (8)

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

Key algorithms: 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

Records

info

10 records at the apex

Found

Read from: 147.78.89.212:53

Type	Value	TTL
SOA	ns1.mcs.de. hostmaster.mcs.de. 2026091400 14400 3600 604800 600	86400
NS	ns2.mcs.de.	86400
NS	ns1.mcs.de.	86400
NS	ns3.mcs.de.	86400
A	141.91.172.100	600
MX	10 mx2.ondataport.de.	3600
MX	10 mx1.ondataport.de.	3600
TXT	"google-site-verification=QXnNaAWJ4CCte2-tPM3iJa1mdEnfc1ym90PerVCFIEc"	3600
TXT	"v=spf1 mx include:dataport.de include:spf.crsend.com -all"	3600
TXT	"google-site-verification=CvngCte7FJHLSxEwK7giF0VLUPlg3LoW3tg48rxrg6U"	3600

Checks

✓ TTLs within range #32

TTLs: A 10m, MX 1h, NS 1d.
✓ 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