Domain report: take-e-way.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

ds.ns-serve.net, ds.nsserve.de

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: ds.ns-serve.net, ds.nsserve.de
NS in the zone: ds.ns-serve.net, ds.nsserve.de

Nameserver	Addresses	Network (AS)	Glue
ds.ns-serve.net	195.191.93.150 2001:67c:2394:3::1002	AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE	-
ds.nsserve.de	195.191.92.150 2001:67c:2394:1::1002	AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ds.ns-serve.net, ds.nsserve.de.

#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 2001:67c:2394::/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 (AS25504 (CRONON-AS - Vautron Rechenzentrum AG, 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
✓ Nameserver names under 2 TLDs #12

Nameserver names use the TLDs .de, .net.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ds.ns-serve.net 195.191.93.150	NOERROR, 14 ms, authoritative	no	yes / yes	refused	Vautron
ds.ns-serve.net 2001:67c:2394:3::1002	NOERROR, 16 ms, authoritative	no	yes / yes	refused	Vautron
ds.nsserve.de 195.191.92.150	NOERROR, 13 ms, authoritative	no	yes / yes	refused	Vautron
ds.nsserve.de 2001:67c:2394:1::1002	NOERROR, 14 ms, authoritative	no	yes / yes	refused	Vautron

Checks

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

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ds.ns-serve.net: "Vautron"; ds.nsserve.de: "Vautron".

#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 1782457758 · primary ds.nsserve.de

Found

Primary (MNAME): ds.nsserve.de
Contact (RNAME): root.ds.nsserve.de
Serial: 1782457758
Refresh / retry: 10800 s / 3600 s
Expire: 604800 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ds.ns-serve.net (195.191.93.150)	1782457758
ds.ns-serve.net (2001:67c:2394:3::1002)	1782457758
ds.nsserve.de (195.191.92.150)	1782457758
ds.nsserve.de (2001:67c:2394:1::1002)	1782457758

Checks

✓ Serial 1782457758 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 ds.nsserve.de is one of the listed nameservers.
✓ Contact root@ds.nsserve.de #25

The SOA RNAME root.ds.nsserve.de means root@ds.nsserve.de.
✓ Timestamp serial #26

The serial 1782457758 is a Unix timestamp (2026-06-26 07:09 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 1 iterations, 1-byte salt
Signatures valid until: 5 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
49951	ECDSAP256SHA256 (13)	SHA256 E271957AF5473EA6…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
49951	KSK (257)	ECDSAP256SHA256 (13)

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

Key algorithms: ECDSAP256SHA256 (13).
✓ Signatures valid until 2026-11-05 #30

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 1 iteration and a 1-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

#31

Records

info

11 records at the apex

Found

Read from: 195.191.93.150:53

Type	Value	TTL
SOA	ds.nsserve.de. root.ds.nsserve.de. 1782457758 10800 3600 604800 3600	86400
NS	ds.nsserve.de.	86400
NS	ds.ns-serve.net.	86400
A	193.218.16.107	3600
MX	0 takeeway-de01f.mail.protection.outlook.com.	3600
TXT	"v=spf1 a mx a:smtp.buhck.de a:rack640.cadeprovider.de mx:smtp.buhck.de ip4:80.156.203.165 ip4:193.218.16.0/24 ip4:84.46.71.0/26 include:spf.protection.outlook.com include:return-cname.emailsys.net -all"	3600
TXT	"atlassian-domain-verification=axdu0b9eXJDwnueMGUDzD3s2GpV/mO1i9wof3v3LspgsPaa3T5yRhhRXv9Ewd6ar"	3600
TXT	"MS=3E9573C322A08675C846CC4BD07269FD9CBCBC35"	3600
TXT	"apple-domain-verification=aqasuYxJ7g7oG7HF"	3600
TXT	"MS=ms52537468"	3600
TXT	"MS=ms77143361"	3600

Checks

✓ TTLs within range #32

TTLs: A 1h, MX 1h, NS 1d.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

#34
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