pnp.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
!Passed with warnings
23 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.vgp.de, ns2.vgp.de, pns.dtag.de, secondary006.dtag.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.vgp.de, ns2.vgp.de, pns.dtag.de, secondary006.dtag.net
NS in the zone
ns1.vgp.de, ns2.vgp.de, pns.dtag.de, secondary006.dtag.net
NameserverAddressesNetwork (AS)Glue
ns1.vgp.de62.157.156.71AS3320 DTAG - Deutsche Telekom AG, DE62.157.156.71
ns2.vgp.de62.157.157.71AS3320 DTAG - Deutsche Telekom AG, DE62.157.157.71
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 ns1.vgp.de, ns2.vgp.de, pns.dtag.de, secondary006.dtag.net.
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS3320 (DTAG - Deutsche Telekom AG, DE): 4 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: ns1.vgp.de, ns2.vgp.de.
    #13

Nameservers

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vgp.de 62.157.156.71NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns2.vgp.de 62.157.157.71NOERROR, 6 ms, authoritativenoyes / yesrefused-
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, 17 ms, authoritativenoyes / yesrefusedDomainNameServer
secondary006.dtag.net 2a00:fa8:3:0:100:0:6:1NOERROR, 20 ms, authoritativenoyes / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 6 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"; secondary006.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 2026101401 · primary ns1.vgp.de

Found

Primary (MNAME)
ns1.vgp.de
Contact (RNAME)
root.vgp.de
Serial
2026101401
Refresh / retry
14400 s / 7200 s
Expire
1209600 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
ns1.vgp.de (62.157.156.71)2026101401
ns2.vgp.de (62.157.157.71)2026101401
pns.dtag.de (194.25.0.125)2026101401
pns.dtag.de (2003:40:8000::100)2026101401
secondary006.dtag.net (195.244.245.25)2026101401
secondary006.dtag.net (2a00:fa8:3:0:100:0:6:1)2026101401

Checks

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

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

19 records at the apex

Found

Read from
62.157.156.71:53
TypeValueTTL
SOAns1.vgp.de. root.vgp.de. 2026101401 14400 7200 1209600 432004000
NSsecondary006.dtag.net.4000
NSns2.vgp.de.4000
NSns1.vgp.de.4000
NSpns.dtag.de.4000
A151.101.2.216600
A151.101.194.216600
A151.101.130.216600
A151.101.66.216600
MX60 mx5.vgp.de.4000
MX70 mx7.vgp.de.4000
MX20 mx4.vgp.de.4000
MX10 mx3.vgp.de.4000
MX60 mx2.vgp.de.4000
MX70 mx6.vgp.de.4000
TXT"atlassian-domain-verification=8f8oL0ETf9ajs1uPqFRgnBZeX1FnDLxGFD2Rv2Vo2GoeCfW6XKpjTruYz36p6Y0T"4000
TXT"v=spf1 mx include:spf.protection.outlook.com ip4:62.157.156.0/23 ip4:162.55.222.7 ip4:85.13.153.162 -all"4000
TXT"MS=ms42161448"4000
TXT"MkBo2F9SC/avaBCFlKts4VezJNTPsfUHeGbR/keJCk3A731vYV4p1ZEswzxtr2Qbe6BADqn8UYxmEXSYwA1Y1A=="4000

Checks

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