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

ns0.wuzer.de, ns2.wuzer.de

Nameserver	Addresses	Network (AS)	Glue
ns0.wuzer.de	62.116.129.129	AS15456 INTERNETX-AS - InterNetX GmbH, DE	62.116.129.129
ns2.wuzer.de	62.116.163.100	AS15456 INTERNETX-AS - InterNetX GmbH, DE	62.116.163.100

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns0.wuzer.de, ns2.wuzer.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.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS15456 (INTERNETX-AS - InterNetX 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

pass

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns0.wuzer.de 62.116.129.129	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns2.wuzer.de 62.116.163.100	NOERROR, 10 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 2019032800 · primary ns0.wuzer.de

Nameserver	Serial
ns0.wuzer.de (62.116.129.129)	2019032800
ns2.wuzer.de (62.116.163.100)	2019032800

✓ Serial 2019032800 everywhere #22

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

SOA refresh 11h5m40s, retry 4h, expire 7d, negative TTL 12h.
✓ Primary is a public nameserver #24

The primary nameserver ns0.wuzer.de is one of the listed nameservers.
✓ Contact edmund@wuzer.de #25

The SOA RNAME edmund.wuzer.de means edmund@wuzer.de.
✓ Date-based serial #26

The serial 2019032800 follows the YYYYMMDDnn convention (2019-03-28).

warn

Not signed

info

4 records at the apex

✓ TTLs within range #32

TTLs: A 6m40s, NS 12h. The NS TTL at the parent is 1d and in the zone 12h; resolvers may use either.
✓ 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