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 & Recommendations262 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, 54 ms lookupPASS
| A | 13.249.74.30, 13.249.74.78, 13.249.74.63, 13.249.74.73 |
| AAAA | — |
| CNAME | — |
| NS | ns-1531.awsdns-63.org, ns-1991.awsdns-56.co.uk, ns-87.awsdns-10.com, ns-926.awsdns-51.net |
| MX | 0 cafepress-com.mail.protection.outlook.com |
| TXT | MS=ms58507112 Validity-Domain-Authentication=qjajdjeuduaja apple-domain-verification=PfJUiRQ0thVKWDzJm01iUHFIhMy7X20XPgZEznC7S0Y facebook-domain-verification=ae8i8zqkrkf7bov2c8d2hq5shm6vrf google-site-verification=-4q6lwBcJYVY9NluEGTdXeUbIlvKfS_iYk6Lv2Me8n0 google-site-verification=M51Z9-MlIpxnBpOba3Wza19Vm2jm-9D3oFcGimGVcs0 google-site-verification=nY82BhHGYsLyjFxw7agxcuQvNnWYhmFdQfiYmrPWX8k idz7e/Ss1cZVMeVBMFBXO5+mnPXWAR79+7K81UAWkgAi3mBXPf8KvXf94y5EvAQpjFTz1Bp+4xZyPxpx... SPF v=spf1 include:amazonses.com ip4:54.173.113.202 include:spf.protection.outlook.c... yandex-verification: 081a63c88656411c |
| 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), 670 ms totalPASS
https://cafepress.com
137 ms · HTTP/1.1
https://www.cafepress.com:443/
533 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cafepress.com | 301 | 137 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.cafepress.com:443/ | 200 | 533 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
User-agent: Googlebot
Disallow:
User-agent: AdsBot-Google
Disallow:
User-agent: Googlebot-image
Disallow:
User-agent: 008
Disallow: /
User-agent: Spinn3r
Disallow: /
User-agent: EtaoSpider
Disallow: /
User-agent: Applebot
Disallow:
user-agent: Pinterestbot
Crawl-delay: 10
User-agent: *
Disallow: /business/secure*
Disallow: /business/*PHPSESSID
Disallow: /business/approve
Disallow: /business/create_item
Disallow: /business/test
Disallow: /business/search
Disallow: /search
# Sitemap files
Sitemap: https://www.cafepress.com/business/sitemap_index.xml
A+Domain Intelligencecafepress.com — via Amazon Registrar, Inc., 29 years, 3 months old, hosted on AWSPASS
336 days
June 19, 2027
262 days
Issued by Amazon
29 years, 3 months
Registered June 20, 1997
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.249.74.78
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