hertz.de

Checked 21 October 2026, 22:50 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 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

info

ns10.hertz.com, ns11.hertz.com, ns12.hertz.com, ns13.hertz.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns10.hertz.com, ns11.hertz.com, ns12.hertz.com, ns13.hertz.com
NS in the zone
ns10.hertz.com, ns11.hertz.com, ns12.hertz.com, ns13.hertz.com
NameserverAddressesNetwork (AS)Glue
ns10.hertz.com205.251.194.131 2600:9000:5302:8300::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns11.hertz.com205.251.199.110 2600:9000:5307:6e00::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns12.hertz.com205.251.193.226 2600:9000:5301:e200::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns13.hertz.com205.251.197.50 2600:9000:5305:3200::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns10.hertz.com, ns11.hertz.com, ns12.hertz.com, ns13.hertz.com.
  • ✓ 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 (AS16509 (AMAZON-02 - Amazon.com, Inc., 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
  • i
    All nameserver names under .com
    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

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns10.hertz.com 205.251.194.131NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns10.hertz.com 2600:9000:5302:8300::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns11.hertz.com 205.251.199.110NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns11.hertz.com 2600:9000:5307:6e00::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns12.hertz.com 205.251.193.226NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns12.hertz.com 2600:9000:5301:e200::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns13.hertz.com 205.251.197.50NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns13.hertz.com 2600:9000:5305:3200::1NOERROR, 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.
  • ✓ 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 1 · primary ns10.hertz.com

Found

Primary (MNAME)
ns10.hertz.com
Contact (RNAME)
awsdns-hostmaster.amazon.com
Serial
1
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns10.hertz.com (205.251.194.131)1
ns10.hertz.com (2600:9000:5302:8300::1)1
ns11.hertz.com (205.251.199.110)1
ns11.hertz.com (2600:9000:5307:6e00::1)1
ns12.hertz.com (205.251.193.226)1
ns12.hertz.com (2600:9000:5301:e200::1)1
ns13.hertz.com (205.251.197.50)1
ns13.hertz.com (2600:9000:5305:3200::1)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns10.hertz.com is one of the listed nameservers.
  • ✓ Contact awsdns-hostmaster@amazon.com #25
    The SOA RNAME awsdns-hostmaster.amazon.com means awsdns-hostmaster@amazon.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
21 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
37889ECDSAP256SHA256 (13)SHA256 16792504931B115C…yes

DNSKEY in the zone

Key tagRoleAlgorithm
46960ZSK (256)ECDSAP256SHA256 (13)
60225ZSK (256)ECDSAP256SHA256 (13)
37889KSK (257)ECDSAP256SHA256 (13)

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 37889 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 2h0m0s and created on demand; the current one was made at 2026-10-21 21:50 UTC and expires at 2026-10-21 23:55 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

13 records at the apex

Found

Read from
205.251.194.131:53
TypeValueTTL
SOAns10.hertz.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 300300
NSns10.hertz.com.300
NSns11.hertz.com.300
NSns12.hertz.com.300
NSns13.hertz.com.300
A45.60.103.53600
A45.60.31.53600
MX10 hccppmx01.hertz.com.3600
MX10 hccppmx02.hertz.com.3600
MX10 htcppmx01.hertz.com.3600
MX10 htcppmx02.hertz.com.3600
TXT"gj5jqtkxsrs9d7c1pfd5bqmbjxvl5bgs"3600
TXT"v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all"3600

Checks

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