Skip to content
https://Bissell.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 7 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.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 32.196.31.0 does not match any cert SAN: ec2-32-196-31-0.compute-1.amazonaws.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 100.30.169.6 does not match any cert SAN: ec2-100-30-169-6.compute-1.amazonaws.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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.Bissell.com/
200https://Bissell.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://Bissell.com/ → https://www.bissell.com:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
2 A records, 49 ms lookup
PASS
2 A records, 49 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 32.196.31.0, 100.30.169.6
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1634.awsdns-12.co.uk, ns-386.awsdns-48.com, ns-1171.awsdns-18.org, ns-664.awsdns-19.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 49 ms
Got: 49 ms
A32.196.31.0, 100.30.169.6
AAAA—
CNAME—
NSns-1634.awsdns-12.co.uk, ns-386.awsdns-48.com, ns-1171.awsdns-18.org, ns-664.awsdns-19.net
MX
0 bissell-com.mail.protection.outlook.com
TXT
klaviyo-site-verification=WQbErU
klaviyo-site-verification=V5jd6E
SPF v=spf1 include:_spf.bissell_com._d.easydmarc.pro ~all
google-site-verification=Ixq_t1z3isXXmgUV6qu8mUXjoNFdXX3McyWxv45lU-0
google-site-verification=qVzYLQpz4re-64-GEKPgk5KRo6NGMxcQw5eAhWGeuMM
klaviyo-site-verification=SSqMZw
openai-domain-verification=dv-43wTOZKqU6ND9x9PXI3EmLiL
anthropic-domain-verification-cmnjck=TmZhYqmkHKBfKf6f3JcEPh0N9
google-site-verification=4HShpWkfGiq5ri-S08g_H7V3nz2hS0FDtSTfcqHcdpY
CAALookup not available with standard resolver
Resolved in 49 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: amazonaws.com, sectigo.com
PASS
issue: amazonaws.com, sectigo.com
Info::
CAA issue tag present — authorized CA(s): amazonaws.com, sectigo.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A
Multi-Resolver DNS Speed
Mean 40ms across 3 resolvers (spread 52ms)
PASS
Mean 40ms across 3 resolvers (spread 52ms)
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Quad9: 74ms
Got: 74ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 562 ms total
PASS
1 redirect(s), 562 ms total
Info::
Single redirect
Got: https://Bissell.com → https://www.bissell.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 562 ms total
Got: 562 ms

https://Bissell.com

308 ms · HTTP/1.1

301

https://www.bissell.com:443/

255 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Bissell.com301308 msHTTP/1.1awselb/2.0
2https://www.bissell.com:443/200255 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 423 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 423 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: http://www.bissell.com/en-us/sitemap_index.xml
Sitemap: http://www.bissell.com/en-ca/sitemap_index.xml

Disallow: */address-information
Disallow: */review-and-pay
Disallow: */order-confirmation
Disallow: */cart
Disallow: */webservices
Disallow: */error
Disallow: */OrderPrint.aspx
Disallow: */search
Disallow: */search?s=*
Disallow: */bhisites
Disallow: */search.aspx?*
Disallow: /on/demandware.store
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
Bissell.com — via CSC Corporate Domains, Inc., 31 years, 2 months old, hosted on AWS
PASS
Bissell.com — via CSC Corporate Domains, Inc., 31 years, 2 months old, hosted on AWS
Info::
Domain registered until Aug 15, 2026 (3 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, 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: AWS
Got: AS14618
Domain expiry

92 days

August 15, 2026

SSL certificate

215 days

Issued by Amazon

Domain age

31 years, 2 months

Registered August 16, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

32.196.31.0

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created August 16, 1995 (31 years, 2 months ago)
Expires August 15, 2026 (3 months)
Last Updated August 11, 2025
Name Servers ns-1171.awsdns-18.org, ns-1634.awsdns-12.co.uk, ns-386.awsdns-48.com, ns-664.awsdns-19.net
DNSSEC Not enabled
Hosting
IP Address 32.196.31.0
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 342 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
101 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
103 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
342 ms
Total Time Total request time from DNS lookup through full response.
342 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 101 ms TLS Handshake 103 ms Server Processing 102 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://Bissell.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://Bissell.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://Bissell.com/health
Got: https://Bissell.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback