Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1099 ms totalFIX
https://couchsurfing.com
384 ms · HTTP/1.1
https://www.couchsurfing.com:443/
541 ms · HTTP/1.1
https://www.couchsurfing.com/welcome
175 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://couchsurfing.com | 301 | 384 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.couchsurfing.com:443/ | 302 | 541 ms | HTTP/1.1 | |
| 3 | https://www.couchsurfing.com/welcome | 200 | 175 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BTLS Certificate Expiry & Recommendations171 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records2 A records, 46 ms lookupPASS
| A | 98.95.82.168, 3.224.166.28 |
| AAAA | — |
| CNAME | — |
| NS | ns-1913.awsdns-47.co.uk, ns-698.awsdns-23.net, ns-414.awsdns-51.com, ns-1086.awsdns-07.org |
| MX | 0 aspmx.l.google.com 10 alt2.aspmx.l.google.com 10 alt1.aspmx.l.google.com 15 aspmx2.googlemail.com 20 aspmx4.googlemail.com 20 aspmx3.googlemail.com 20 aspmx5.googlemail.com |
| TXT | google-site-verification=-57CcthqTPu9wEzF_D2mJK4AJsZCJGcfB6dmNkVxbUE google-site-verification=dePtB2FQiPj959WiuZ6mxuMi8SQo2Bk1qMRtYdjWCEI gumk7ml9fr3ds8jgogh5k0p6vo google-site-verification=4Z9cqbgraS5pvYlR46HbxdvmyorahG7VctkNTmWdcg8 google-site-verification=Xbyq11M9UWFdbu1BBXFPrYTrVSMFi-M5vOYtKBagZnM google-site-verification=7sIFE7rqtb4Dc7qf9vOan2zxsnlIUiVpLE2ZwbQvtcc SPF v=spf1 include:_spf.google.com include:sendgrid.net include:spf.sendingservice.n... fdle7l8bs5r22e6od3ip630ohh google-site-verification=ttiuLt4NeinX8Mx82Mk5n-PcfErnkGRPs2JgojNaUjo |
| 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+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
User-agent: ADmantX
Disallow: /
User-agent: Twitterbot
Disallow: /admin
User-agent: *
Disallow: /admin
Sitemap: https://www.couchsurfing.com/root_sitemap.xml
Host: www.couchsurfing.com
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecouchsurfing.com — via Register.com - Network Solutions, LLC, 27 years, 3 months old, hosted on AWSPASS
2921 days
June 13, 2034
171 days
Issued by Amazon
27 years, 3 months
Registered June 13, 1999
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.224.166.28
Register.com - 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