bayern3.de

Checked 21 October 2026, 21:36 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 4 info

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

warn

dns-2.br.de, dns-3.br.de, ns-1.br.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns-2.br.de, dns-3.br.de, ns-1.br.de
NS in the zone
dns-2.br.de, dns-3.br.de, ns-1.br.de
NameserverAddressesNetwork (AS)Glue
dns-2.br.de35.195.140.130AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US35.195.140.130
dns-3.br.de34.77.85.13AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US34.77.85.13
ns-1.br.de194.187.162.130AS35739 BRNET - Bayerischer Rundfunk, DE194.187.162.130

Checks

  • ✓ 3 nameservers #6
    Delegated to dns-2.br.de, dns-3.br.de, ns-1.br.de.
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS35739 (BRNET - Bayerischer Rundfunk, DE): 1 address; AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US): 2 addresses.
  • 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

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns-2.br.de 35.195.140.130NOERROR, 11 ms, authoritativenoyes / yesrefused-
dns-3.br.de 34.77.85.13NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-1.br.de 194.187.162.130NOERROR, 13 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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.

SOA

pass

serial 2026101301 · primary ns-1.br.de

Found

Primary (MNAME)
ns-1.br.de
Contact (RNAME)
hostmaster.br.de
Serial
2026101301
Refresh / retry
43200 s / 7200 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns-2.br.de (35.195.140.130)2026101301
dns-3.br.de (34.77.85.13)2026101301
ns-1.br.de (194.187.162.130)2026101301

Checks

  • ✓ Serial 2026101301 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 28d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns-1.br.de is one of the listed nameservers.
  • ✓ Contact hostmaster@br.de #25
    The SOA RNAME hostmaster.br.de means hostmaster@br.de.
  • ✓ Date-based serial #26
    The serial 2026101301 follows the YYYYMMDDnn convention (2026-10-13).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

10 records at the apex

Found

Read from
35.195.140.130:53
TypeValueTTL
SOAns-1.br.de. hostmaster.br.de. 2026101301 43200 7200 2419200 36003600
NSdns-2.br.de.3600
NSns-1.br.de.3600
NSdns-3.br.de.3600
A194.187.162.1743600
MX0 bayern3-de.mail.protection.outlook.com.3600
TXT"v=spf1 include:spf.protection.outlook.com ip4:185.118.144.91 ip4:185.118.144.89 -all"3600
TXT"google-site-verification=GrC_883dVQJf9WlD3b0N2L2k_jnqmyyEFMzeVkYcV-w"3600
TXT"MS=ms34552321"3600
TXT"facebook-domain-verification=29lafpnqu7a7zxc7sxoq6nqyqyug45"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 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