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

ns1.redirectdom.com, ns2.redirectdom.com

Nameserver	Addresses	Network (AS)	Glue
ns1.redirectdom.com	168.119.46.105	AS24940 HETZNER-AS - Hetzner Online GmbH, DE	-
ns2.redirectdom.com	51.195.125.195	AS16276 OVH - OVH SAS, FR	-

i

2 nameservers

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

#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 0 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address.
i

All nameserver names under .com

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

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.redirectdom.com 168.119.46.105	NOERROR, 2 ms, authoritative	no	yes / yes	refused	-
ns2.redirectdom.com 51.195.125.195	NOERROR, 6 ms, authoritative	no	yes / yes	refused	-

✓ 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.
✓ 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 2026092401 · primary ns1.redirectdom.com

Nameserver	Serial
ns1.redirectdom.com (168.119.46.105)	2026092401
ns2.redirectdom.com (51.195.125.195)	2026092401

✓ Serial 2026092401 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 ns1.redirectdom.com is one of the listed nameservers.
✓ Contact dnsmaster@ns1.redirectdom.com #25

The SOA RNAME dnsmaster.ns1.redirectdom.com means dnsmaster@ns1.redirectdom.com.
✓ Date-based serial #26

The serial 2026092401 follows the YYYYMMDDnn convention (2026-09-24).

warn

Not signed

info

4 records at the apex

Type	Value	TTL
SOA	ns1.redirectdom.com. dnsmaster.ns1.redirectdom.com. 2026092401 10800 3600 604800 3600	3600
NS	ns1.redirectdom.com.	3600
NS	ns2.redirectdom.com.	3600
A	49.13.50.5	3600

✓ TTLs within range #32

TTLs: A 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