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
BTLS Certificate Expiry & Recommendations186 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BCDN & DeliveryVercelREVIEW
ADNS Records1 A records, 978 ms lookupPASS
| A | 76.76.21.21 |
| AAAA | — |
| CNAME | — |
| NS | ns1.getgo.com, ns2.getgo.com, ns3.getgo.com |
| MX | 10 mx0b-001a0901.pphosted.com 10 mx0a-001a0901.pphosted.com |
| TXT | onetrust-domain-verification=880138feaded4baa9ee494cb6aaac351 MS=ms44780740 google-site-verification=eTmStxfPaGc78p88Tm9pKCWxcs3JNr6DSScIi2H_wPQ 00491296 mixpanel-domain-verify=31f8d6bc-db0e-4718-b0d0-0c3a77cb123f google-site-verification=qmJ6lnS-rF5bK57cVsXKPRZAtGzUPXL9bNWILKmFnNo docusign=616bdb3b-e921-4b9d-b19a-39e645f46083 _kdqswptomjbxuvoyzk9wcwkya09hllk stripe-verification=B5E8F5E7FDED4E598204E05361206FF2788B58FC1D5AB52C9A8051A73AD2... anthropic-domain-verification-n3fwn5=ePGTNNcEEwCcPZnS0O1KchSqN lucid-verification=IJOahq5oO1hS03KgtmAa miro-verification=88bfcf1a779dd19255e9c4f29499682b1f8666fd slack-domain-verification=VC9f5p13Iv20kSPO3gBBMYzqa4sf6n4uRF2hz5wE google-site-verification=bP1za2CWM0J8J-9KTFFDuO9IgJfc9Urp3U1YmYrraK8 apple-domain-verification=yh4UFAPU6mYDPMCR google-site-verification=4Gkpa3cO8Iw68Jl3xG86XwEbBGpE45suVh0OeTl0HqM stripe-verification=741C78E7C8BE1FA61D462791DC7EFDB17183445B1CAD231302D3E22CBDBD... _vhufhwzfd08qthl81vefkuyejzu0nam atlassian-domain-verification=d0nBtThU9bX2e05DrbRkm9BjYjlKuh3wJecaSP3peE9D/W7+dr... SPF v=spf1 redirect=goto.com.hosted.spf-report.com canva-site-verification=5c5EAjFCWdx-8-C5bP3-7Q jetbrains-domain-verification=89z710kd1tpazxp3mw6aqpp23 _e5qian675kqkfcvf2owb3nspw3x4hd0 stripe-verification=002DDA1078C0BE29EA835F5D1DC61D86717A28238EFD1A2D25AB4BB889D1... N7etLn7xNX6B29OJ-oTU5A druide-validation-domaine=5859499cd3041804cf8c2390a4ca68ff |
| 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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ARedirect Chain1 redirect(s), 831 ms totalPASS
https://goto.com
190 ms · HTTP/1.1
https://www.goto.com/
641 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://goto.com | 301 | 190 ms | HTTP/1.1 | Vercel |
| 2 | https://www.goto.com/ | 200 | 641 ms | HTTP/1.1 | Vercel |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 2190 URLsPASS
User-agent: *
Allow: /
Disallow: /users/
Disallow: /search/
Disallow: /index.php
Disallow: /collections/
Disallow: /d/search
Sitemap: https://www.goto.com/sitemap.xml
Sitemap: https://www.goto.com/es/sitemap.xml
Sitemap: https://www.goto.com/it/sitemap.xml
Sitemap: https://www.goto.com/fr/sitemap.xml
Sitemap: https://www.goto.com/pt/sitemap.xml
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencegoto.com — via Nom-iq Ltd. dba COM LAUDE, 28 years, 3 months old, hosted on AWSPASS
361 days
June 10, 2027
186 days
Issued by DigiCert Inc
28 years, 3 months
Registered June 11, 1998
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
76.76.21.21
Nom-iq Ltd. dba COM LAUDE
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