Domain report: bmvg.de

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

pns.dtag.de, secondary004.dtag.net

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: pns.dtag.de, secondary004.dtag.net
NS in the zone: pns.dtag.de, secondary004.dtag.net

Nameserver	Addresses	Network (AS)	Glue
pns.dtag.de	194.25.0.125 2003:40:8000::100	AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE	194.25.0.125 2003:40:8000::100
secondary004.dtag.net	195.244.245.27 2a00:fa8:3:0:100:0:4:1	AS5605 NETUSE - NetUSE AG, DE AS5605 NETUSE - NetUSE AG, DE	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pns.dtag.de, secondary004.dtag.net.

#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 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS3320 (DTAG - Deutsche Telekom AG, DE): 2 addresses; AS5605 (NETUSE - NetUSE AG, DE): 2 addresses.
✓ Nameserver names under 2 TLDs #12

Nameserver names use the TLDs .de, .net.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
pns.dtag.de 194.25.0.125	NOERROR, 10 ms, authoritative	no	yes / yes	refused	DomainNameServer
pns.dtag.de 2003:40:8000::100	NOERROR, 7 ms, authoritative	no	yes / yes	refused	DomainNameServer
secondary004.dtag.net 195.244.245.27	NOERROR, 12 ms, authoritative	no	yes / yes	refused	DomainNameServer
secondary004.dtag.net 2a00:fa8:3:0:100:0:4:1	NOERROR, 16 ms, authoritative	no	yes / yes	refused	DomainNameServer

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.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: pns.dtag.de: "DomainNameServer"; secondary004.dtag.net: "DomainNameServer".

#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 2025018589 · primary pns.dtag.de

Found

Primary (MNAME): pns.dtag.de
Contact (RNAME): hostmaster.bundeswehr.org
Serial: 2025018589
Refresh / retry: 36000 s / 3600 s
Expire: 2419200 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
pns.dtag.de (194.25.0.125)	2025018589
pns.dtag.de (2003:40:8000::100)	2025018589
secondary004.dtag.net (195.244.245.27)	2025018589
secondary004.dtag.net (2a00:fa8:3:0:100:0:4:1)	2025018589

Checks

✓ Serial 2025018589 everywhere #22

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

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

The primary nameserver pns.dtag.de is one of the listed nameservers.
✓ Contact hostmaster@bundeswehr.org #25

The SOA RNAME hostmaster.bundeswehr.org means hostmaster@bundeswehr.org.
✓ Timestamp serial #26

The serial 2025018589 is a Unix timestamp (2034-03-03 17:09 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 10 iterations, 7-byte salt
Signatures valid until: 24 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
18716	RSASHA256 (8)	SHA256 4C1C60D0FEDB890D…	yes
38560	RSASHA256 (8)	SHA256 31194239567155A8…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
29700	ZSK (256)	RSASHA256 (8)
13531	ZSK (256)	RSASHA256 (8)
38560	KSK (257)	RSASHA256 (8)
18716	KSK (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 18716 (SHA256), key tag 38560 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Short-lived signatures (online signing) #30

Signatures are valid for 97h0m0s and created on demand; the current one was made at 2026-10-20 18:13 UTC and expires at 2026-10-24 18:45 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 10 iterations and a 7-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

#31

Records

info

7 records at the apex

Found

Read from: 194.25.0.125:53

Type	Value	TTL
SOA	pns.dtag.de. hostmaster.bundeswehr.org. 2025018589 36000 3600 2419200 86400	3600
NS	pns.dtag.de.	3600
NS	secondary004.dtag.net.	3600
A	91.221.59.45	3600
MX	0 .	3600
TXT	"v=spf1 -all"	3600
TXT	"_telesec-domain-validation=359342_2026-09-21_125Yvbnt5PHRm6sZwhD8eGI7YSVbeYSivYli52Ak1tDS3AxrNx"	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.
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