picr.de

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

warn

ns.routing.net, ns8.routing.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.routing.net, ns8.routing.net
NS in the zone
ns.routing.net, ns8.routing.net
NameserverAddressesNetwork (AS)Glue
ns.routing.net134.0.30.178AS48823 AS48823 - Hosting.de GmbH, DE-
ns8.routing.net194.50.113.2AS41637 ROUTING-ANYCAST - Hosting.de GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.routing.net, ns8.routing.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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS41637 (ROUTING-ANYCAST - Hosting.de GmbH, DE): 1 address; AS48823 (AS48823 - Hosting.de GmbH, DE): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.routing.net 134.0.30.178NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns8.routing.net 194.50.113.2NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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 2026033101 · primary ns.routing.net

Found

Primary (MNAME)
ns.routing.net
Contact (RNAME)
hostmaster.geotraq.de
Serial
2026033101
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns.routing.net (134.0.30.178)2026033101
ns8.routing.net (194.50.113.2)2026033101

Checks

  • ✓ Serial 2026033101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.routing.net is one of the listed nameservers.
  • ✓ Contact hostmaster@geotraq.de #25
    The SOA RNAME hostmaster.geotraq.de means hostmaster@geotraq.de.
  • ✓ Date-based serial #26
    The serial 2026033101 follows the YYYYMMDDnn convention (2026-03-31).

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

6 records at the apex

Found

Read from
134.0.30.178:53
TypeValueTTL
SOAns.routing.net. hostmaster.geotraq.de. 2026033101 14400 3600 604800 9003600
NSns.routing.net.3600
NSns8.routing.net.3600
A144.76.166.124900
MX10 mx.geotraq.de.3600
TXT"v=spf1 mx a ip4:148.251.83.207 ip4:144.76.166.124 ip4:138.201.190.189 include:_spf.google.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, 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