Skip to content
https://heinz.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
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
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.heinz.com/
200https://heinz.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://heinz.com/ https://heinz.com:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google, 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google, 1.1 google
A
DNS Records
1 A records, 44 ms lookup
PASS
1 A records, 44 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.149.219.19
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns1.cscdns.net, dns2.cscdns.net
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 44 ms
Got: 44 ms
A34.149.219.19
AAAA
CNAME
NSdns1.cscdns.net, dns2.cscdns.net
MX
TXT
google-site-verification=KhdkDbCenCj93xTmVX-4omRt3FNuaYxsMkj-kpXVqMs
CAALookup not available with standard resolver
Resolved in 44 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

https://heinz.com

66 ms · HTTP/1.1

301

https://www.heinz.com/

232 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://heinz.com30166 msHTTP/1.1
2https://www.heinz.com/200232 msHTTP/1.1Google Frontend

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1964 URLs
PASS
robots.txt present, sitemap with 1964 URLs
Info::
robots.txt is present
Got: 66 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1964 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 66 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://www.heinz.com/sitemap.xml

A+
Domain Intelligence
heinz.com — via CSC Corporate Domains, Inc., 28 years, 9 months old, hosted on Google Cloud
PASS
heinz.com — via CSC Corporate Domains, Inc., 28 years, 9 months old, hosted on Google Cloud
Info::
Domain registered until Nov 17, 2026 (7 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: CSC Corporate Domains, Inc.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

127 days

November 17, 2026

SSL certificate

106 days

Issued by Sectigo Limited

Domain age

28 years, 9 months

Registered November 18, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.149.219.19

Registrar

CSC Corporate Domains, Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar CSC Corporate Domains, Inc.
Created November 18, 1997 (28 years, 9 months ago)
Expires November 17, 2026 (7 months)
Last Updated November 13, 2025
Name Servers dns1.cscdns.net, dns2.cscdns.net
DNSSEC Enabled
Hosting
IP Address 34.149.219.19
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.4s)
A+
HTTP Probe Timing
Total 105 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
42 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
27 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
105 ms
Total Time Total request time from DNS lookup through full response.
105 ms

Connection waterfall

DNS Lookup 42 ms TCP Connect 17 ms TLS Handshake 27 ms Server Processing 19 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