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

ns.rheinbahn.de, ns2.rheinbahn.de

Nameserver	Addresses	Network (AS)	Glue
ns.rheinbahn.de	194.31.227.34	AS49609 INTERSOLUTE - Intersolute GmbH, DE	194.31.227.34
ns2.rheinbahn.de	194.31.227.42	AS49609 INTERSOLUTE - Intersolute GmbH, DE	194.31.227.42

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.rheinbahn.de, ns2.rheinbahn.de.

#6
✓ 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: ns.rheinbahn.de, ns2.rheinbahn.de.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
!

Nameservers in one network

all IPv4 addresses are in 194.31.227.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS49609 (INTERSOLUTE - Intersolute GmbH, DE): 2 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

fail

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns.rheinbahn.de 194.31.227.34	NOERROR, 40 ms, authoritative	no	yes / yes	ALLOWED (470 records)	DNS
ns2.rheinbahn.de 194.31.227.42	NOERROR, 39 ms, authoritative	no	yes / yes	refused	DNS

✓ All respond #14

All 2 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.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns.rheinbahn.de: "DNS"; ns2.rheinbahn.de: "DNS".

#17
✗

Zone transfer allowed

These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns.rheinbahn.de (194.31.227.34): 470 records. Restrict zone transfers to your secondary servers.

#18
✓ 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.

warn

serial 2026102101 · primary ns.rheinbahn.de

Nameserver	Serial
ns.rheinbahn.de (194.31.227.34)	2026102101
ns2.rheinbahn.de (194.31.227.42)	2026102101

✓ Serial 2026102101 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

refresh 7d is outside 20m–1d; negative caching TTL (minimum) 7d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 7d, retry 1d, expire 28d, negative TTL 7d.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns.rheinbahn.de is one of the listed nameservers.
✓ Contact administrator@rheinbahn.de #25

The SOA RNAME administrator.rheinbahn.de means administrator@rheinbahn.de.
✓ Date-based serial #26

The serial 2026102101 follows the YYYYMMDDnn convention (2026-10-21).

warn

Signed, but no DS at parent

Key tag	Role	Algorithm
12590	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-01 #30

The earliest DNSKEY/SOA signature expires at 2026-11-01 08:58 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

14 records at the apex

Type	Value	TTL
SOA	ns.rheinbahn.de. administrator.rheinbahn.de. 2026102101 604800 86400 2419200 604800	300
NS	ns.rheinbahn.de.	300
NS	ns2.rheinbahn.de.	300
A	194.31.227.210	300
MX	20 mx2.rheinbahn.de.	300
MX	10 mx1.rheinbahn.de.	300
TXT	"AJyIm2FHboBPQQdRRsgd4740NsY5piPWShlROrEbWpqMCuHzImtNd2QRgP969PhuFc7vAKUiU1WhzeO7hvEluQ=="	3600
TXT	"google-site-verification=bIcBFuNC0YRQbny6LsOiSV6wO4ftFsjxtA6K_n2XXvs"	3600
TXT	"facebook-domain-verification=gj20z43vivr57q6kacrwyd1yma99o4"	3600
TXT	"v=spf1 mx a:mx3.rheinbahn.de a:mx4.rheinbahn.de -all"	3600
TXT	"hDiUA3C4eh51VQJY7CXW86rNR5e3Zo5n"	3600
TXT	"apple-domain-verification=CFKaImqFUIdQ5wy3"	3600
TXT	"apple-domain-verification=XVFuLjNVLCOmSkzZ"	3600
TXT	"jrzvhj0ll0dg5mwfltdhd2zpxd1tl7qf"	3600

✓ TTLs within range #32

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