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

ns01.snafu.de, ns02.snafu.de

Nameserver	Addresses	Network (AS)	Glue
ns01.snafu.de	213.73.103.2	AS34171 SNAFU-LIG-AS - snafu Gesellschaft fuer interaktive Netzwerke mbH, DE	213.73.103.2
ns02.snafu.de	78.46.25.196	AS24940 HETZNER-AS - Hetzner Online GmbH, DE	78.46.25.196

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.snafu.de, ns02.snafu.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.
✓ 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: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS34171 (SNAFU-LIG-AS - snafu Gesellschaft fuer interaktive Netzwerke mbH, DE): 1 address.
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

info

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns01.snafu.de 213.73.103.2	NOERROR, 13 ms, authoritative	no	yes / yes	refused	snafu_dns
ns02.snafu.de 78.46.25.196	NOERROR, 3 ms, authoritative	no	yes / yes	refused	snafu_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: ns01.snafu.de: "snafu_dns"; ns02.snafu.de: "snafu_dns".

#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 2026102002 · primary ns01.snafu.de

Nameserver	Serial
ns01.snafu.de (213.73.103.2)	2026102002
ns02.snafu.de (78.46.25.196)	2026102002

✓ Serial 2026102002 everywhere #22

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

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

The primary nameserver ns01.snafu.de is one of the listed nameservers.
✓ Contact domain@team.snafu.de #25

The SOA RNAME domain.team.snafu.de means domain@team.snafu.de.
✓ Date-based serial #26

The serial 2026102002 follows the YYYYMMDDnn convention (2026-10-20).

warn

Not signed

info

8 records at the apex

Type	Value	TTL
SOA	ns01.snafu.de. domain.team.snafu.de. 2026102002 86400 7200 604800 86400	86400
NS	ns01.snafu.de.	86400
NS	ns02.snafu.de.	86400
A	213.73.98.172	7200
MX	1 mx.mymailwall.com.	7200
TXT	"spcheck=18e79846bd5e19616b525a6cc8b81b8f16f21fadc72e2f11f53d1942fc313e94"	7200
TXT	"google-site-verification=s6OGYch058hcfghYdYx9Mt3mPZ2Wh0mNB8MIfUaMUiI"	7200
TXT	"v=spf1 include:spf.protection.outlook.com include:mymailwall.com ip4:213.73.105.213 -all"	7200