datenschutz-mv.de

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

ns.mvnet.de, ns2.mvnet.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.mvnet.de, ns2.mvnet.de
NS in the zone
ns.mvnet.de, ns2.mvnet.de
NameserverAddressesNetwork (AS)Glue
ns.mvnet.de85.208.248.100 2a02:1006:c000:0:194:25:108:10AS198435 DVZ-AS - DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH, DE AS198435 DVZ-AS - DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH, DE85.208.248.100 2a02:1006:c000:0:194:25:108:10
ns2.mvnet.de85.208.250.51 2a02:1006:c000:0:195:145:109:51AS198435 DVZ-AS - DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH, DE AS198435 DVZ-AS - DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH, DE85.208.250.51 2a02:1006:c000:0:195:145:109:51

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.mvnet.de, ns2.mvnet.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a02:1006:c000::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS198435 (DVZ-AS - DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH, DE): 4 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.mvnet.de 85.208.248.100NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns.mvnet.de 2a02:1006:c000:0:194:25:108:10NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.mvnet.de 85.208.250.51NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.mvnet.de 2a02:1006:c000:0:195:145:109:51NOERROR, 12 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 3000000538 · primary ns.mvnet.de

Found

Primary (MNAME)
ns.mvnet.de
Contact (RNAME)
hostmaster.mvnet.de
Serial
3000000538
Refresh / retry
14400 s / 1800 s
Expire
2592000 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns.mvnet.de (85.208.248.100)3000000538
ns.mvnet.de (2a02:1006:c000:0:194:25:108:10)3000000538
ns2.mvnet.de (85.208.250.51)3000000538
ns2.mvnet.de (2a02:1006:c000:0:195:145:109:51)3000000538

Checks

  • ✓ Serial 3000000538 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, expire 30d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.mvnet.de is one of the listed nameservers.
  • ✓ Contact hostmaster@mvnet.de #25
    The SOA RNAME hostmaster.mvnet.de means hostmaster@mvnet.de.
  • ✓ Timestamp serial #26
    The serial 3000000538 is a Unix timestamp (2065-01-24 05:28 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
100 iterations, 16-byte salt
Signatures valid until
3 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
24014RSASHA256 (8)SHA256 91A6D45148481254…yes

DNSKEY in the zone

Key tagRoleAlgorithm
38178ZSK (256)RSASHA256 (8)
24014KSK (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 24014 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-03 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-03 17:13 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 100 iterations and a 16-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

10 records at the apex

Found

Read from
85.208.248.100:53
TypeValueTTL
SOAns.mvnet.de. hostmaster.mvnet.de. 3000000538 14400 1800 2592000 18001800
NSns2.mvnet.de.1800
NSns.mvnet.de.1800
A85.208.250.411800
MX10 mx03.mvnet.de.1800
MX10 mx04.mvnet.de.1800
TXT"cisco-ci-domain-verification=7496e5edc4b340b7cdb00aedcaf8216ea40e0dec643d6ae123e9686a02932712"1800
TXT"D-TRUST=WMRFXF5BYZIYW55PU8GT8RC"1800
TXT"v=spf1 include:_spf.dvz-mv.de -all"1800
TXT"apple-domain-verification=J7kglcMj3KisNcum"1800

Checks

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