dvag.de

Checked 21 October 2026, 22:15 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

info

ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
NS in the zone
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-04.azure-dns.com13.107.236.4 2603:1061:0:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-04.azure-dns.net150.171.21.4 2620:1ec:8ec:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-04.azure-dns.org204.14.183.4 2a01:111:4000:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-04.azure-dns.info208.84.5.4 2620:1ec:bda:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-04.azure-dns.com 13.107.236.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-04.azure-dns.com 2603:1061:0:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 150.171.21.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 2620:1ec:8ec:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 204.14.183.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 2a01:111:4000:700::4NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns4-04.azure-dns.info 208.84.5.4NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-04.azure-dns.info 2620:1ec:bda:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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: ns4-04.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". 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 1 · primary ns1-04.azure-dns.com

Found

Primary (MNAME)
ns1-04.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-04.azure-dns.com (13.107.236.4)1
ns1-04.azure-dns.com (2603:1061:0:700::4)1
ns2-04.azure-dns.net (150.171.21.4)1
ns2-04.azure-dns.net (2620:1ec:8ec:700::4)1
ns3-04.azure-dns.org (204.14.183.4)1
ns3-04.azure-dns.org (2a01:111:4000:700::4)1
ns4-04.azure-dns.info (208.84.5.4)1
ns4-04.azure-dns.info (2620:1ec:bda:700::4)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-04.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

21 records at the apex

Found

Read from
13.107.236.4:53
TypeValueTTL
SOAns1-04.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300300
NSns1-04.azure-dns.com.3600
NSns2-04.azure-dns.net.3600
NSns3-04.azure-dns.org.3600
NSns4-04.azure-dns.info.3600
A151.101.3.10300
A151.101.67.10300
A151.101.131.10300
A151.101.195.10300
MX0 dvag-de.mail.protection.outlook.com.300
TXT"v=spf1 ip4:84.201.22.187 a:outbound.dvag.de include:spf.protection.outlook.com include:cust-spf.exacttarget.com a:outbound.produktion.cloud.dvag ~all"300
TXT"apple-domain-verification=c948rE4vVgYucpTG"300
TXT"have-i-been-pwned-verification=01ad02edba628342ee4f15a1081b5121"300
TXT"_mlx8lviz8hx5bevdtqgvpc90zdec1sd"300
TXT"MS=ms63013655"300
TXT"openai-domain-verification=dv-TFnIRp9P7i0KLn8yvQnfVLDd"300
CAA0 issue "digicert.com"300
CAA0 issue "letsencrypt.org"300
CAA0 issuewild "letsencrypt.org"300
CAA0 issuewild "digicert.com"300
CAA0 iodef "mailto:domains@dvag.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, letsencrypt.org.