brandenburg.de

Checked 21 October 2026, 21:54 UTC · via 8.8.8.8
!Passed with warnings
27 passed 1 warning 0 failed 5 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

info

ns1.brandenburg.de, ns4.variomedia.de, pns.brandenburg.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.brandenburg.de, ns4.variomedia.de, pns.brandenburg.de
NS in the zone
ns1.brandenburg.de, ns4.variomedia.de, pns.brandenburg.de
NameserverAddressesNetwork (AS)Glue
ns1.brandenburg.de194.76.232.165AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE194.76.232.165
ns4.variomedia.de81.28.232.230 2a00:1c38::4:53AS29014 SCALEUP - ScaleUp Technologies GmbH & Co. KG, DE AS29014 SCALEUP - ScaleUp Technologies GmbH & Co. KG, DE-
pns.brandenburg.de194.76.232.129AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE194.76.232.129

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.brandenburg.de, ns4.variomedia.de, pns.brandenburg.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.brandenburg.de, pns.brandenburg.de.
  • ✓ 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 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS29014 (SCALEUP - ScaleUp Technologies GmbH & Co. KG, DE): 2 addresses; AS680 (DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE): 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.brandenburg.de, pns.brandenburg.de.
    #13

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.brandenburg.de 194.76.232.165NOERROR, 13 ms, authoritativenoyes / yesrefusedPublic DNS server v28.3.2. Keep your hands off!
ns4.variomedia.de 81.28.232.230NOERROR, 17 ms, authoritativenoyes / yesrefusedBIND
ns4.variomedia.de 2a00:1c38::4:53NOERROR, 17 ms, authoritativenoyes / yesrefusedBIND
pns.brandenburg.de 194.76.232.129NOERROR, 13 ms, authoritativenoyes / yesrefusedPublic DNS server v28.3.2. Keep your hands off!

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.brandenburg.de: "Public DNS server v28.3.2. Keep your hands off!"; pns.brandenburg.de: "Public DNS server v28.3.2. Keep your hands off!". Hide or replace the version string.
    #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 2026102019 · primary pns.brandenburg.de

Found

Primary (MNAME)
pns.brandenburg.de
Contact (RNAME)
vpnadmin.brandenburg.de
Serial
2026102019
Refresh / retry
28800 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.brandenburg.de (194.76.232.165)2026102019
ns4.variomedia.de (81.28.232.230)2026102019
ns4.variomedia.de (2a00:1c38::4:53)2026102019
pns.brandenburg.de (194.76.232.129)2026102019

Checks

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

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
12 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
385RSASHA256 (8)SHA256 E1C3F6A075A01E6A…yes

DNSKEY in the zone

Key tagRoleAlgorithm
35650ZSK (256)RSASHA256 (8)
385KSK (257)RSASHA256 (8)

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 385 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-12 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-12 23:59 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

pass

24 records at the apex

Found

Read from
194.76.232.165:53
TypeValueTTL
SOApns.brandenburg.de. vpnadmin.brandenburg.de. 2026102019 28800 7200 1209600 86400600
NSpns.brandenburg.de.600
NSns4.variomedia.de.600
NSns1.brandenburg.de.600
A194.76.232.226600
AAAA2001:638:81a::2600
MX10 pmmx-hea-p01.brandenburg.de.600
MX10 pmmx-hea-p02.brandenburg.de.600
TXT"v=spf1 mx ip4:194.76.232.119 ip4:194.76.232.120 ip4:194.76.232.208 ip4:194.76.232.217 ip4:194.76.232.222 ip4:194.76.232.223 ip4:194.76.232.224 ip4:193.28.249.33 ip4:193.28.241.133 ~all"600
TXT"_telesec-domain-validation=362456_2026-09-10_hp04R6HbT4nWZNZgnSEJ9pQSgCSKlZgpZih9PTkvf1XyiV9O4H"600
TXT"rovag_verification_token=D88F7C686C8440B2A0037C7ADB802948"600
TXT"google-site-verification=w8dEVksQpCsO7p0UFmr4_UBjIV4OHjBGiOe9rwfH-CI"600
TXT"HARICA-iHiAiJhfMZxIbGxm9Yt"600
TXT"u0r1kgq369h3vo9j1ftpl47snh"600
CAA0 issuewild "telesec.de"600
CAA0 issue "pki.dfn.de"600
CAA0 iodef "mailto:vpnadmin@zit-bb.brandenburg.de"600
CAA0 issue "harica.gr"600
CAA0 issue "d-trust.de"600
CAA0 issue "letsencrypt.org"600
CAA0 issuewild "d-trust.de"600
CAA0 issuewild "letsencrypt.org"600
CAA0 issue "godaddy.com"600
CAA0 issue "telesec.de"600

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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: telesec.de, pki.dfn.de, harica.gr, d-trust.de, letsencrypt.org, godaddy.com.