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 & Recommendations137 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 & DeliveryGoogle Cloud CDNREVIEW
A+DNS Records2 A records, 78 ms lookupPASS
| A | 67.199.248.15, 67.199.248.14 |
| AAAA | — |
| CNAME | — |
| NS | ns-cloud-b4.googledomains.com, ns-1053.awsdns-03.org, ns-880.awsdns-46.net, ns-cloud-b2.googledomains.com, ns-1689.awsdns-19.co.uk, ns-cloud-b1.googledomains.com, ns-343.awsdns-42.com, ns-cloud-b3.googledomains.com |
| MX | 10 aspmx.l.google.com 20 alt2.aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 aspmx2.googlemail.com 30 aspmx3.googlemail.com |
| TXT | atlassian-domain-verification=Th+HeZjMKa3QxX9JqLt67kxMrAsEfB9gz51iuPZYjYbveQXnML... slack-domain-verification=OsqnOPaJcFcYkul1EcF9xRDbjgCiaBgdXHbq2uuC SPF v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_net... yandex-verification: 641fdbe43ac1cd41 MS=ms65999994 google-site-verification=At4Yo9DrDstvlkL5TvBE-n7NDY1e8oXHDZ0zfBPl39c status-page-domain-verification=cfzktt77bqp2 google-site-verification=Vus6M9ONzl9cle6IlSjKu8EhefYSY0_-zt4COS8c0j4 E906595EB8 |
| 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.
A+Redirect ChainNo redirects — direct accessPASS
https://bitly.com
115 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bitly.com | 200 | 115 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
# Welcome to Bitly =)
# robots welcome;
# API documentation can be found at https://dev.bitly.com/
User-Agent: *
Disallow: /pages/landing
Disallow: /pages/*/landing
Disallow: /pages/pt$
Disallow: /pages/home
Disallow: /pages/*/home
Disallow: /pages/thank-you
Disallow: /pages/de/danke
Disallow: /pages/fr/merci
Disallow: /pages/it/grazie
Disallow: /pages/es/gracias
Disallow: /*/demo-thank-you
Disallow: /*/email-thank-you
Disallow: /*/partner-agreement
Disallow: /*/free-plan-refresh-faqs
Disallow: /*/automatic-renewal-terms
Disallow: /*/domain-name-use-agreement
Disallow: /*/cookie-policy
Disallow: /pages/pricing/*
Disallow: /pages/*/pricing/*
Disallow: /pages/*/v1$
Disallow: /pages/*/v2$
Disallow: /blog/?p=
Disallow: /blog/page/*/?p=
Disallow: /pages/*?preview[
Disallow: /pages/*&preview[
Disallow: /pages/*[
Disallow: /pages/*{
Disallow: /pages/*;
User-agent: PetalBot
User-agent: ChatGPT Agent
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
User-agent: ByteDance
Crawl-delay: 1
Sitemap: https://bitly.com/pages/sitemap_index.xml
Sitemap: https://bitly.com/blog-hub/sitemap-index.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebitly.com — via GoDaddy.com, LLC, 22 years, 9 months old, hosted on Google CloudPASS
119 days
November 12, 2026
137 days
Issued by Amazon
22 years, 9 months
Registered November 12, 2003
Not enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
67.199.248.14
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