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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations280 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records4 A records, 100 ms lookupPASS
| A | 108.157.98.65, 108.157.98.59, 108.157.98.123, 108.157.98.114 |
| AAAA | — |
| CNAME | — |
| NS | ns-1546.awsdns-01.co.uk, ns-877.awsdns-45.net, ns-492.awsdns-61.com, ns-1154.awsdns-16.org |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com |
| TXT | figma-domain-verification=b23172d6bafae2639adba798417030ea57cc5c66cca26c7cf77ca1... jamf-site-verification=6KsOa_hXIoFYcs4U-ycnGA atlassian-domain-verification=o25iIe9Jr805+vUZ13KF3VgHHNejIxdx/y/sC+JI2Be9B1l1k2... miro-verification=c238eb19a3900f9022b2dd2cee65b3349c066da0 openai-domain-verification=dv-sFO9QxPN3BBHE1KXLGxZPC8y docker-verification=3287867a-69cf-46a8-9aac-3c92a32d5931 mixpanel-domain-verify=007c418c-57b5-4cca-8f6a-69edd6c0c9cf adobe-idp-site-verification=b2e6a69046947a884c67879d015ac98d7c7157d7d43e1ddec34c... MS=D8F5E4617F05614D8674B9BECB8617008F9FCE5F google-site-verification=TTJxyytJxoTs_D15KV_M2QxIPSaSnP8FEeFJq1yfwBc salesforce-site-verification=00D30000000nSwR=1TBPP00000000o1 MS=ms61425939 facebook-domain-verification=35hphhsn4jyqmnl8qwo23ueaiy742y slack-domain-verification=3ALq7edkoq85Y3yC0TFToUZoEGZsb7rrnFhpcTb9 wrike-verification=MTkyNzcwOjJiNmU1YjkxYTFiZjVjYTE0Mzg3OWQyZjQ3NGI2NzkyMmM0YTdkY... hubspot-developer-verification=NzM1MjU1NDItODZkYS00NTViLWIwMzgtOTBhNmVjZTMzMGJi drift-domain-verification=fa680538bbf6219a4e863967839197daecee409d4f0bc0490a5d8d... proxy-ssl.webflow.com SPF v=spf1 mx ip4:62.13.150.16 ip4:174.36.80.216 ip4:174.36.80.219 ip4:208.117.56.91... pendo-domain-verification=982b640c-494d-487f-9972-2dccee7e0f02 cursor-domain-verification-phdyjj=nDMmX4tGKrO4wYNRxzoJZoqMe ZOOM_verify_yPO0JA7fJsrOu249Sf7ljn google-site-verification=PzoR99ZmmcJcmXoleVcFM4aHT2_qb9F_48ee1SL2SD0 |
| 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.
ARedirect Chain1 redirect(s), 273 ms totalPASS
https://hootsuite.com
113 ms · HTTP/1.1
https://www.hootsuite.com/
160 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://hootsuite.com | 301 | 113 ms | HTTP/1.1 | |
| 2 | https://www.hootsuite.com/ | 200 | 160 ms | HTTP/1.1 | Vercel |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 3767 URLsPASS
User-agent: *
Disallow: *d=pro*
Disallow: /*?*srsltid
Disallow: /dashboard*
Disallow: /signup*
Disallow: /feed*
Disallow: /login*
Disallow: /hootlet/social-share*
Disallow: /hootlet/load*
Disallow: /social-connect/send*
Disallow: /share-button*
Disallow: /app/social-network/*
Disallow: /ajax*
Disallow: /sso-redirect*
Disallow: /js*
Disallow: /craft/
Disallow: /*.pdf$
Disallow: /billing/
Disallow: /create-free-account*
Disallow: /academy-free-account*
Disallow: /content-generator-embed*
Sitemap: https://www.hootsuite.com/sitemap.xml
Host: https://www.hootsuite.com
- https://www.hootsuite.com/industries/cpg
- https://www.hootsuite.com/whats-new/quarter-end-product-update
- https://www.hootsuite.com/whats-new/yeti-agent-page-aware-answers
- https://www.hootsuite.com/whats-new/edit-link-previews-aka-cards-for-x
- https://www.hootsuite.com/whats-new/do-more-with-smarter-planner-controls
A+Domain Intelligencehootsuite.com — via GoDaddy.com, LLC, 17 years, 5 months old, hosted on AWSPASS
395 days
July 16, 2027
280 days
Issued by Amazon
17 years, 5 months
Registered January 21, 2009
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
108.157.98.59
GoDaddy.com, 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