Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/1 IPs match cert SANREVIEW
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 & Recommendations78 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
BCDN & DeliveryVercelREVIEW
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 36 ms lookupPASS
| A | 216.150.1.1 |
| AAAA | — |
| CNAME | — |
| NS | thaddeus.ns.cloudflare.com, leia.ns.cloudflare.com |
| MX | 29 route3.mx.cloudflare.net 72 route2.mx.cloudflare.net 92 route1.mx.cloudflare.net |
| TXT | google-site-verification=f-CCPtzWSGbBomEUhSgCUsGGg84zIGkCVw5W5f14QaY SPF v=spf1 include:_spf.mx.cloudflare.net ~all tiktok-developers-site-verification=OrweL2JUuCnoWvRtVEEe6lrgjd8ugdzX tiktok-developers-site-verification=fmnAJ8EoG5MD6f4WSPKjn7shGuexD1n4 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 39ms across 3 resolvers (spread 35ms)PASS
ARedirect Chain1 redirect(s), 254 ms totalPASS
https://scanracer.com
102 ms · HTTP/1.1
https://scanracer.com/fr
152 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://scanracer.com | 308 | 102 ms | HTTP/1.1 | Vercel |
| 2 | https://scanracer.com/fr | 200 | 152 ms | HTTP/1.1 | Vercel |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 2924 URLsPASS
User-Agent: *
Allow: /
Disallow: /api
Disallow: /auth
Disallow: /login
Disallow: /signup
Disallow: /upload
Disallow: /profile
Disallow: /profile/edit
Disallow: /search
Disallow: /newsletter/confirmed
Disallow: /newsletter/unsubscribed
Disallow: /pro/success
Disallow: /pro/cancel
Disallow: /fr/api
Disallow: /fr/auth
Disallow: /fr/login
Disallow: /fr/signup
Disallow: /fr/upload
Disallow: /fr/profile
Disallow: /fr/profile/edit
Disallow: /fr/search
Disallow: /fr/newsletter/confirmed
Disallow: /fr/newsletter/unsubscribed
Disallow: /fr/pro/success
Disallow: /fr/pro/cancel
Disallow: /en/api
Disallow: /en/auth
Disallow: /en/login
Disallow: /en/signup
Disallow: /en/upload
Disallow: /en/profile
Disallow: /en/profile/edit
Disallow: /en/search
Disallow: /en/newsletter/confirmed
Disallow: /en/newsletter/unsubscribed
Disallow: /en/pro/success
Disallow: /en/pro/cancel
User-Agent: Mediapartners-Google
Allow: /
User-Agent: Google-Display-Ads-Bot
Allow: /
Host: https://scanracer.com
Sitemap: https://scanracer.com/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencescanracer.com — via Cloudflare, Inc., 6 months old, hosted on AWSPASS
162 days
February 4, 2027
78 days
Issued by Let's Encrypt
6 months
Registered February 4, 2026
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
216.150.1.1
Cloudflare, 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