Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations80 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records2 A records, 31 ms lookupPASS
| A | 104.17.118.12, 104.17.117.12 |
| AAAA | 2606:4700::6811:760c, 2606:4700::6811:750c |
| CNAME | — |
| NS | amy.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 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect Chain0 redirect(s), 70 ms totalPASS
https://stripchat.com
70 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://stripchat.com | 406 | 70 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 1198 URLsPASS
# 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 Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencestripchat.com — via Amazon Registrar, Inc., 20 years, 5 months oldPASS
974 days
February 13, 2029
80 days
Issued by Google Trust Services
20 years, 5 months
Registered February 13, 2006
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6811:750c
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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