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
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /fastajax/*
Disallow: /fastajax/order/*
Disallow: /fastajax/order/tax/*
Disallow: /fastajax/order/tax/validatevat*
Disallow: *ajax?*
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations65 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- 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 & DeliveryGoogle Cloud CDNREVIEW
A+DNS Records1 A records, 197 ms lookupPASS
| A | 35.227.253.10 |
| AAAA | — |
| CNAME | — |
| NS | ns4.siteground.com, ns3.siteground.com, ns2.siteground.com, ns1.siteground.com |
| MX | 10 mx10.antispam.mailspamprotection.com 20 mx20.antispam.mailspamprotection.com 30 mx30.antispam.mailspamprotection.com |
| TXT | google-site-verification=zqCisYNqVi7cNNl62eSC9WVM-aZBheLfKaR3-tdOmvA google-site-verification=eq5Y2zXODoC3uls0LpprPQfdZvRrkvG2q_InXwDAtVE _globalsign-domain-verification=u53IVPzwq3sVZGZmcS7n7V4uRo4O266M55PygUGxcf google-site-verification=Lyklcr075dYiiD5aJtOv9vTJrUZk8qAWyd7av7LPfEo SPF v=spf1 include:_spf.siteground.com include:_spf.google.com include:_spf.mailspam... |
| 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
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), 619 ms totalPASS
https://siteground.com
287 ms · HTTP/1.1
https://www.siteground.com/
331 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://siteground.com | 301 | 287 ms | HTTP/1.1 | nginx |
| 2 | https://www.siteground.com/ | 200 | 331 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencesiteground.com — via Tucows Domains Inc., 22 years, 4 months old, hosted on Google CloudPASS
1375 days
March 22, 2030
65 days
Issued by Google Trust Services
22 years, 4 months
Registered March 22, 2004
Not enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
35.227.253.10
Tucows Domains 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