Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations134 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
A+DNS Records4 A records, 47 ms lookupPASS
| A | 3.165.113.96, 3.165.113.32, 3.165.113.34, 3.165.113.81 |
| AAAA | — |
| CNAME | — |
| NS | ns-1579.awsdns-05.co.uk, ns-585.awsdns-09.net, ns-147.awsdns-18.com, ns-1402.awsdns-47.org |
| MX | 10 stripes-com.mail.protection.outlook.com |
| TXT | MS=ms79523019 MS=ms16312950 oxF1pYkBFTlGK8AU2csAcr6RlkVqk5vHwEltDU+qCZpnHOV3vAg5Dm75TgYiA0jTV7WW9EcgqcbmzWfB... _1um3f0zsgf9ntbtd9pfwhehvikxfwai vsf8pxcf6dfknp9qzl0t42d6ty9w8z2x SPF v=spf1 include:outlook.com include:amazonses.com include:mail.zendesk.com includ... google-site-verification=Td4vrwQkiWditw20ABi0n1PBbJFmQGdiATKefwYb3bE |
| 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.
ARedirect Chain1 redirect(s), 742 ms totalPASS
https://stripes.com
307 ms · HTTP/1.1
https://www.stripes.com/
436 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://stripes.com | 301 | 307 ms | HTTP/1.1 | Varnish |
| 2 | https://www.stripes.com/ | 200 | 436 ms | HTTP/1.1 | nginx/1.28.0 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
# -------------------------------
# Sitemap locations
# -------------------------------
Sitemap: https://www.stripes.com/sitemap/sitemap-index.xml
Sitemap: https://europe.stripes.com/sitemap/sitemap-index.xml
Sitemap: https://korea.stripes.com/sitemap/sitemap-index.xml
Sitemap: https://guam.stripes.com/sitemap/sitemap-index.xml
Sitemap: https://okinawa.stripes.com/sitemap/sitemap-index.xml
Sitemap: https://japan.stripes.com/sitemap/sitemap-index.xml
# -------------------------------
# Block specific AI bots
# -------------------------------
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: FacebookBot
Disallow: /
# -------------------------------
# Googlebot-specific directives
# -------------------------------
User-agent: *
# Block migration content/directory
Disallow: /migration/
# Block URLs with specific query parameters
Disallow: /*?_evDiscoveryPath=
Disallow: /*?subcategory=
Disallow: /*?*subcategory*
Disallow: /*?*utm_source=
Disallow: /*?*utm_campaign=
Disallow: /*?*utm_medium=
Disallow: /*?offset=
Disallow: /*?count=
Disallow: /*?total=
# Block old Polopolly article URLs with numeric IDs at the end (e.g., -1.647382)
Disallow: /*-1.*
A+Domain Intelligencestripes.com — via Network Solutions, LLC, 31 years, 11 months old, hosted on AWSPASS
868 days
October 31, 2028
134 days
Issued by Amazon
31 years, 11 months
Registered November 1, 1994
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.165.113.32
Network Solutions, LLC
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