Skip to content
https://bit.ly

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
5 PASS 4 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 123 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 123 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# Welcome to Bitly =)
# robots welcome;
# API documentation can be found at https://dev.bitly.com/
User-Agent: *
Disallow:

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
146 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

146
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 67.199.248.11, 67.199.248.10
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns-1372.awsdns-43.org, ns-1766.awsdns-28.co.uk, ns-276.awsdns-34.com, ns-705.awsdns-24.net, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 7 ms
Got: 7 ms
A67.199.248.11, 67.199.248.10
AAAA
CNAME
NSns-1372.awsdns-43.org, ns-1766.awsdns-28.co.uk, ns-276.awsdns-34.com, ns-705.awsdns-24.net, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
2205ECE8B9
9ab819f3-2495-4611-856e-26a99cb9e4ba
MS=ms11124067
anthropic-domain-verification-tzcmah=HSWn0K6bK99Nsdu2zAo6rVUnK
apple-domain-verification=6YYbatV9m7YWHrdw
atlassian-domain-verification=Th+HeZjMKa3QxX9JqLt67kxMrAsEfB9gz51iuPZYjYbveQXnML...
google-site-verification: zhEwFAQvtUWYInQtt81loDiZmomsEmkAbuRsSSxk1YI
miro-verification=fac1aeff65bb8e30ec8efd62a6ba02f2ce19a82c
openai-domain-verification=dv-enGte8sEHDo7E13TnxTOPn5k
slack-domain-verification=MkeV937L2HSoy5NFJUcwGD4mo6Qguojp2v8Ny0oX
SPF v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_net...
yandex-verification: 41b3ec866726729d
CAALookup not available with standard resolver
Resolved in 7 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 532 ms total
PASS
1 redirect(s), 532 ms total
Info::
Single redirect
Got: https://bit.ly → https://bitly.com/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://bit.ly
Info::
Redirect overhead: 532 ms total
Got: 532 ms
Info::
Cross-domain redirect detected

https://bit.ly

260 ms · HTTP/1.1

302

https://bitly.com/

271 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bit.ly302260 msHTTP/1.1nginx
2https://bitly.com/200271 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.bit.ly/
200https://bit.ly/

Preferred variant: non-www

HTTP → HTTPS

302http://bit.ly/ https://bitly.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
bit.ly — via Libyan Spider Network (int), 18 years, 2 months old, hosted on Google Cloud
PASS
bit.ly — via Libyan Spider Network (int), 18 years, 2 months old, hosted on Google Cloud
Info::
Domain registered until May 17, 2032 (6 years, 2 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Libyan Spider Network (int)
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

2135 days

May 17, 2032

SSL certificate

146 days

Issued by Amazon

Domain age

18 years, 2 months

Registered May 17, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

67.199.248.10

Registrar

Libyan Spider Network (int)

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Libyan Spider Network (int)
Created May 17, 2008 (18 years, 2 months ago)
Expires May 17, 2032 (6 years, 2 months)
Last Updated April 18, 2022
Name Servers ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com, ns-705.awsdns-24.net, ns-1372.awsdns-43.org
DNSSEC Not enabled
Hosting
IP Address 67.199.248.10
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (1.7s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 257 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
2 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
257 ms
Total Time Total request time from DNS lookup through full response.
257 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 2 ms TLS Handshake 5 ms Server Processing 249 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback