Skip to content
https://stripchat.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
100
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
406 HTTP 406
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
80 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
A+
DNS Records
2 A records, 31 ms lookup
PASS
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.118.12, 104.17.117.12
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6811:760c, 2606:4700::6811:750c
Info::
2 nameserver(s) configured
Got: amy.ns.cloudflare.com, duke.ns.cloudflare.com
Info::
7 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: 31 ms
Got: 31 ms
A104.17.118.12, 104.17.117.12
AAAA2606:4700::6811:760c, 2606:4700::6811:750c
CNAME
NSamy.ns.cloudflare.com, duke.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx4.googlemail.com
10 aspmx3.googlemail.com
10 aspmx5.googlemail.com
10 aspmx2.googlemail.com
TXT
SPF v=spf1 include:spf.stripchat.com -all
google-site-verification=S8ShtOSN2AUxiDZbsiDUtsIdx7Jr8CtTa_wTlnI5bwI
mailru-verification: aa18f9ab0def0b70
google-site-verification=iduZu8D3ZgE5M1MqS-Rkvldi6SCThQwlVs4u27etGNU
google-site-verification=TBV_95JbDODhguSUqTs45WSpw1H4nff5VD0Zd1imj-c
CAALookup not available with standard resolver
Resolved in 31 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
0 redirect(s), 70 ms total
PASS
0 redirect(s), 70 ms total

https://stripchat.com

70 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://stripchat.com40670 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6811:760c, 2606:4700::6811:750c
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700::6811:760c, 2606:4700::6811:750c Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 1198 URLs
PASS
robots.txt present, sitemap with 1198 URLs
Info::
robots.txt is present
Got: 530 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1198 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 530 B Sitemaps referenced 8 User-agents * Blocking No — crawling allowed
# generated automatically
              
User-agent: *
Disallow: /user/
Disallow: /confirm-email/
Disallow: /messages/
Disallow: */filter/*

Sitemap: https://stripchat.com/sitemap.xml
Sitemap: https://stripchat.com/sitemap-index.xml
Sitemap: https://stripchat.com/sitemap-photos.xml
Sitemap: https://stripchat.com/sitemap-videos.xml
Sitemap: https://stripchat.com/sitemap-search.xml 
Sitemap: https://stripchat.com/sitemap-galleries.xml
Sitemap: https://stripchat.com/mixed-tags.xml
Sitemap: https://stripchat.com/blog/sitemap.xml
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.stripchat.com/
200https://stripchat.com/

Preferred variant: non-www

HTTP → HTTPS

301http://stripchat.com/ https://stripchat.com/

Consistent

A+
Domain Intelligence
stripchat.com — via Amazon Registrar, Inc., 20 years, 5 months old
PASS
stripchat.com — via Amazon Registrar, Inc., 20 years, 5 months old
Info::
Domain registered until Feb 13, 2029 (2 years, 10 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: Amazon Registrar, 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.
Domain expiry

974 days

February 13, 2029

SSL certificate

80 days

Issued by Google Trust Services

Domain age

20 years, 5 months

Registered February 13, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6811:750c

Registrar

Amazon Registrar, Inc.

Unlocked 2 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 Amazon Registrar, Inc.
Created February 13, 2006 (20 years, 5 months ago)
Expires February 13, 2029 (2 years, 10 months)
Last Updated June 20, 2024
Name Servers amy.ns.cloudflare.com, duke.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6811:750c
Data source: rdap (0.2s)

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 101 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 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.
21 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
102 ms
Total Time Total request time from DNS lookup through full response.
102 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 35 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9ed5203a9ac6d11d-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9ed5203a9ac6d11d-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback