Skip to content
https://hertz.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 1429 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 1429 B Sitemaps referenced 2 User-agents Googlebot, Googlebot-Image, AdsBot-Google-Mobile, Storebot-Google, *, AdsBot-Google, APIs-Google, Mediapartners-Google, Googlebot-News Blocking No — crawling allowed
User-agent: Googlebot

User-agent: Googlebot-Image

User-agent: AdsBot-Google

User-agent: APIs-Google

User-agent: Mediapartners-Google

User-agent: AdsBot-Google-Mobile

User-agent: Googlebot-News

User-agent: Storebot-Google

Disallow: /rentacar/car-hire/

Disallow: /rentacar/byr/

Disallow: /rentacar/handlers/

Disallow: /rentacar/null-

Disallow: /rentacar/manage-cookies

Disallow: */rentacar/templates/integrated/*

Disallow: */rentacar/emember/*

Disallow: */rentacar/error/*

Disallow: */location/templates/*

Disallow: */rentacar/fts/*

Disallow: */rentacar/b2b/index.jsp*

Disallow: */rentacar/dandc/templates/*

Disallow: */rentacar/destinationindex/*

Disallow: /rentacar/customersupport/index.jsp?targetPage=faqsView.jsp

Allow: */rentacar/assets/*



User-Agent: * 

Disallow: /rentacar/car-hire/

Disallow: /rentacar/byr/

Disallow: /rentacar/handlers/

Disallow: /rentacar/null-

Disallow: /rentacar/manage-cookies

Disallow: */rentacar/templates/integrated/*

Disallow: */rentacar/emember/*

Disallow: */rentacar/error/*

Disallow: */rentacar/fts/*

Disallow: */rentacar/b2b/index.jsp*

Disallow: */rentacar/dandc/templates/*

Disallow: */rentacar/assets/*

Disallow: */rentacar/destinationindex/*

Disallow: /rentacar/customersupport/index.jsp?targetPage=faqsView.jsp


Host: https://www.hertz.com

Sitemap: https://www.hertz.com/hertz-sitemap.xml

Sitemap: https://www.hertz.com/us/en.sitemap-index.xml
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.hertz.com/
200https://hertz.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://hertz.com/ https://hertz.com/

Consistent

B
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

88
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 47 ms lookup
PASS
2 A records, 47 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 45.60.31.5, 45.60.103.5
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns10.hertz.com, ns12.hertz.com, ns13.hertz.com, ns11.hertz.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 47 ms
Got: 47 ms
A45.60.31.5, 45.60.103.5
AAAA
CNAME
NSns10.hertz.com, ns12.hertz.com, ns13.hertz.com, ns11.hertz.com
MX
10 mxa-00034201.gslb.pphosted.com
10 mxb-00034201.gslb.pphosted.com
TXT
hcp-domain-verification=76317e220ea53155c8e3b08e6918889dd0feb9b2cd393cc3e56f3ed8...
amazonses:/IPm1hhpAyQ6uAN3f5XmTLtE6VZpUY582Ppr6IOcIVU=
cursor-domain-verification-02kyt0=YhujnsBIJtSktCMqhZ8r9sAT9
infoblox-domain-mastery=7ada838ff03c6654eac9005e99b87df0bd7804a0345fa5e54ca2d91c...
_globalsign-domain-verification=-jzefWdoUCJxai9FWTvTDdRNc9N2JJFgFuKXH3uf7r
msfpkey=3bh3x8yaiq2v4u7299q3pav40
parkable-domain-verification=ioyWPZCFOHUtBmZ_91fSt7_cqzkzGzQWnH1sEFD_Mow=
spf2.0/pra ip4:66.216.133.19 ip4:66.109.239.154 ip4:66.109.242.2 ?all
_globalsign-domain-verification=vUVVHjKXy36YMW7WkfvJI7TFHsdwQfNbN7Zk3ADeci
MS=ms13411640
ff965r3f3xkp2dmt55k49yhvx2ssydw6
atlassian-domain-verification=UIjQlEnCPaW6i0RzVM3AR436tSaICZapas/EUtMfpkfZBIa0JM...
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
CAALookup not available with standard resolver
Resolved in 47 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 445 ms total
PASS
1 redirect(s), 445 ms total
Info::
Single redirect
Got: https://hertz.com → https://www.hertz.com/ (301)
Info::
WWW normalization redirect

https://hertz.com

332 ms · HTTP/1.1

301

https://www.hertz.com/

113 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hertz.com301332 msHTTP/1.1
2https://www.hertz.com/200113 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A
Domain Intelligence
hertz.com — via MarkMonitor Inc., 30 years, 2 months old, hosted on INCAPSULA - Incapsula Inc, US
PASS
hertz.com — via MarkMonitor Inc., 30 years, 2 months old, hosted on INCAPSULA - Incapsula Inc, US
Warning::
Domain expires in 69 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 1, 2026
Info::
DNSSEC is enabled
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: INCAPSULA - Incapsula Inc, US
Got: AS19551
Domain expiry

17 days

July 1, 2026

SSL certificate

88 days

Issued by GlobalSign nv-sa

Domain age

30 years, 2 months

Registered July 2, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

INCAPSULA - Incapsula Inc, US

ASN AS19551

45.60.103.5

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created July 2, 1996 (30 years, 2 months ago)
Expires July 1, 2026 (2 months)
Last Updated June 11, 2025
Name Servers ns10.hertz.com, ns11.hertz.com, ns12.hertz.com, ns13.hertz.com
DNSSEC Enabled
Hosting
IP Address 45.60.103.5
ASN AS19551 (INCAPSULA - Incapsula Inc, US)
Provider INCAPSULA - Incapsula Inc, US
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 325 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
92 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
94 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
325 ms
Total Time Total request time from DNS lookup through full response.
325 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 92 ms TLS Handshake 94 ms Server Processing 93 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback