Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNS Records2 A records, 31 ms lookupREVIEW
| A | 172.66.157.101, 104.20.44.139 |
| AAAA | 2606:4700:10::6814:2c8b, 2606:4700:10::ac42:9d65 |
| CNAME | www.scaleway.com.cdn.cloudflare.net |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
BTLS Certificate Expiry & Recommendations318 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- 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
ARedirect Chain1 redirect(s), 154 ms totalPASS
https://www.scaleway.com
68 ms · HTTP/1.1
https://www.scaleway.com/en/
86 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.scaleway.com | 301 | 68 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.scaleway.com/en/ | 200 | 86 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 7 URLsPASS
User-Agent: *
Disallow: /?tags=
Disallow: /?utm
Disallow: /?q=
Disallow: /?a=
Disallow: /?facetFilters=
Disallow: /?route=
Disallow: /?page=
Disallow: /?vat_rate=
Disallow: /?ref=
Disallow: /?pk_campaign=
Disallow: /?source=
Disallow: /?amp=
Disallow: /?btag=
Disallow: /?mode=
Disallow: /?s=
Disallow: /?do=
Disallow: /?rev=
Disallow: /?trk=
Disallow: /?attachment_id=
Disallow: /?from=
Disallow: /?email=
Disallow: /?discounts=
Disallow: /?family=
Disallow: /?gclid=
Sitemap: https://www.scaleway.com/sitemap.xml
- https://www.scaleway.com/sitemaps/sitema...
- https://www.scaleway.com/sitemaps/sitema...
- https://www.scaleway.com/sitemaps/sitema...
- https://www.scaleway.com/sitemaps/sitema...
- https://www.scaleway.com/sitemaps/sitema...
- https://www.scaleway.com/en/docs/sitemap...
- https://www.scaleway.com/en/docs/tutoria...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencescaleway.com — via Scaleway SAS, 18 years, 7 months oldPASS
136 days
November 25, 2026
318 days
Issued by Sectigo Limited
18 years, 7 months
Registered November 25, 2007
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::ac42:9d65
Scaleway SAS
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
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