jurpc.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 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

ns1.vistec.net, ns2.vistec.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.vistec.net, ns2.vistec.net
NS in the zone
ns1.vistec.net, ns2.vistec.net
NameserverAddressesNetwork (AS)Glue
ns1.vistec.net213.216.11.47 2a02:13c0::11:47AS20792 VISTEC-AS - VISTEC Internet Service GmbH, DE AS20792 VISTEC-AS - VISTEC Internet Service GmbH, DE-
ns2.vistec.net212.71.195.66 2001:14f8:1:7::1:11AS12502 NEPUSTILNET-AS01 - Dr.-Ing. Nepustil & Co. GmbH Internet Service Center Ingenieurgesellschaft fuer Systemsoftware und Kommunikationstechnik, DE AS12502 NEPUSTILNET-AS01 - Dr.-Ing. Nepustil & Co. GmbH Internet Service Center Ingenieurgesellschaft fuer Systemsoftware und Kommunikationstechnik, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.vistec.net, ns2.vistec.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: AS12502 (NEPUSTILNET-AS01 - Dr.-Ing. Nepustil & Co. GmbH Internet Service Center Ingenieurgesellschaft fuer Systemsoftware und Kommunikationstechnik, DE): 2 addresses; AS20792 (VISTEC-AS - VISTEC Internet Service GmbH, DE): 2 addresses.
  • i
    All nameserver names under .net
    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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vistec.net 213.216.11.47NOERROR, 5 ms, authoritativenoyes / yesrefusedBIND
ns1.vistec.net 2a02:13c0::11:47NOERROR, 5 ms, authoritativenoyes / yesrefusedBIND
ns2.vistec.net 212.71.195.66NOERROR, 7 ms, authoritativenoyes / yesrefusedBIND
ns2.vistec.net 2001:14f8:1:7::1:11NOERROR, 7 ms, authoritativenoyes / yesrefusedBIND

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: ns1.vistec.net: "BIND"; ns2.vistec.net: "BIND".
    #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

warn

serial 2026091403 · primary ns.vistec.com

Found

Primary (MNAME)
ns.vistec.com
Contact (RNAME)
root.ns.vistec.com
Serial
2026091403
Refresh / retry
86400 s / 14400 s
Expire
1209600 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns1.vistec.net (213.216.11.47)2026091403
ns1.vistec.net (2a02:13c0::11:47)2026091403
ns2.vistec.net (212.71.195.66)2026091403
ns2.vistec.net (2001:14f8:1:7::1:11)2026091403

Checks

  • ✓ Serial 2026091403 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 4h, expire 14d, negative TTL 2d.
    #23
  • i
    Hidden master
    The primary nameserver ns.vistec.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@ns.vistec.com #25
    The SOA RNAME root.ns.vistec.com means root@ns.vistec.com.
  • ✓ Date-based serial #26
    The serial 2026091403 follows the YYYYMMDDnn convention (2026-09-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

11 records at the apex

Found

Read from
213.216.11.47:53
TypeValueTTL
SOAns.vistec.com. root.ns.vistec.com. 2026091403 86400 14400 1209600 1728003600
NSns2.vistec.net.3600
NSns1.vistec.net.3600
A185.158.133.13600
MX5 alt1.aspmx.l.google.com.3600
MX1 aspmx.l.google.com.3600
MX10 aspmx2.googlemail.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX10 aspmx3.googlemail.com.3600
TXT"google-site-verification=daG639Who2B3jbqFpYOaRW5oCIGy61m6tL0AOBlJ_2c"3600
TXT"v=spf1 ip4:213.216.6.0/24 ip4:213.216.4.224/28 ip4:213.216.10.176/28 include:_spf.google.com ~all"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.
  • ✓ 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