fritz-berger.de

Checked 21 October 2026, 22:31 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 2 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

fail

ac01.fritz-berger.de, cs01.fritz-berger.de, pns.dtag.de, secondary006.dtag.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ac01.fritz-berger.de, cs01.fritz-berger.de, pns.dtag.de, secondary006.dtag.net
NS in the zone
ac01.fritz-berger.de, pns.dtag.de, secondary006.dtag.net
NameserverAddressesNetwork (AS)Glue
ac01.fritz-berger.de195.145.144.209AS3320 DTAG - Deutsche Telekom AG, DE195.145.144.209
cs01.fritz-berger.de (parent only)(does not resolve)195.145.144.210
pns.dtag.de194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.0.125 2003:40:8000::100
secondary006.dtag.net195.244.245.25 2a00:fa8:3:0:100:0:6:1AS5605 NETUSE - NetUSE AG, DE AS5605 NETUSE - NetUSE AG, DE-

Checks

  • ✓ 4 nameservers #6
    Delegated to ac01.fritz-berger.de, cs01.fritz-berger.de, pns.dtag.de, secondary006.dtag.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: cs01.fritz-berger.de. ac01.fritz-berger.de, pns.dtag.de, secondary006.dtag.net report NS ac01.fritz-berger.de pns.dtag.de secondary006.dtag.net.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ac01.fritz-berger.de, cs01.fritz-berger.de.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): cs01.fritz-berger.de.
    #9
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS3320 (DTAG - Deutsche Telekom AG, DE): 3 addresses; AS5605 (NETUSE - NetUSE AG, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ac01.fritz-berger.de.
    #13

Nameservers

fail

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ac01.fritz-berger.de 195.145.144.209NOERROR, 6 ms, authoritativenoyes / yesALLOWED (122 records)9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.10
pns.dtag.de 194.25.0.125NOERROR, 9 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100NOERROR, 10 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary006.dtag.net 195.244.245.25NOERROR, 12 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary006.dtag.net 2a00:fa8:3:0:100:0:6:1NOERROR, 16 ms, authoritativenoyes / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 5 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ac01.fritz-berger.de: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.10". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ac01.fritz-berger.de (195.145.144.209): 122 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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

warn

serial 2026090301 · primary ac01.fritz-berger.de

Found

Primary (MNAME)
ac01.fritz-berger.de
Contact (RNAME)
edv.fritz-berger.de
Serial
2026090301
Refresh / retry
600 s / 3600 s
Expire
3600000 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
ac01.fritz-berger.de (195.145.144.209)2026090301
pns.dtag.de (194.25.0.125)2026090301
pns.dtag.de (2003:40:8000::100)2026090301
secondary006.dtag.net (195.244.245.25)2026090301
secondary006.dtag.net (2a00:fa8:3:0:100:0:6:1)2026090301

Checks

  • ✓ Serial 2026090301 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 10m is outside 20m–1d; retry 1h should be shorter than refresh 10m. Current values: refresh 10m, retry 1h, expire 1000h, negative TTL 12h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ac01.fritz-berger.de is one of the listed nameservers.
  • ✓ Contact edv@fritz-berger.de #25
    The SOA RNAME edv.fritz-berger.de means edv@fritz-berger.de.
  • ✓ Date-based serial #26
    The serial 2026090301 follows the YYYYMMDDnn convention (2026-09-03).

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

12 records at the apex

Found

Read from
195.145.144.209:53
TypeValueTTL
SOAac01.fritz-berger.de. edv.fritz-berger.de. 2026090301 600 3600 3600000 43200600
NSsecondary006.dtag.net.600
NSpns.dtag.de.600
NSac01.fritz-berger.de.600
A49.13.41.88600
AAAA2a01:4f8:1c1d:133::1600
MX50 castor.fritz-berger.de.600
MX51 mailgw.fritz-berger.de.600
TXT"v=spf1 a mx ip4:195.145.144.212 ip4:195.145.144.211 " "ip4:213.198.99.210 ip4:213.198.99.211 ip4:81.25.202.82 " "ip4:85.236.50.85 ip6:2001:4178:2:1032:fb::1 " "include:spf.de.umantis.com " "include:_spf.salesforce.com ~all"3600
TXT"MS=ms71876680"3600
TXT"pinterest-site-verification=8b54831efb566fdfd2b8b325768a1815"3600
TXT"facebook-domain-verification=fx910w5085l615o6gh759pfd734et2"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, MX 10m, NS 10m. The NS TTL at the parent is 1d and in the zone 10m; 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