Skip to content
https://bitbucket.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 870 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 870 B Sitemaps referenced 0 User-agents *, 008 Blocking No — crawling allowed
User-Agent: *
Disallow: /api/
Disallow: /!api/
Disallow: /*/changesets/
Disallow: /*/changeset/
Disallow: /*/commits/
Disallow: /*/full-commit/
Disallow: /*/annotate/
Disallow: /*/history/
Disallow: /*/follow/
Disallow: /*/get/*
Disallow: /*/diff/
Disallow: /*/search/
Disallow: /*/fork/
Disallow: /*/pull/
Disallow: /*/hack/
Disallow: /*/raw/*
Disallow: /*.diff$
Disallow: /news/*/$
Disallow: /*/zealots/
Disallow: /*/descendants/
Disallow: /*?status=
Disallow: /*?reported_by=
Disallow: /*?kind=
Disallow: /*?q=
Disallow: /*?name=
Disallow: /*?receiver=
Disallow: /xhr/*
Disallow: /*/atom/
Disallow: /*/rss/
Disallow: /*/compare/*
Disallow: /*/src/*
Disallow: /*/history-node/*

Disallow: /jerkstore/*
Disallow: /npln/*

# Google Site Link Exclusions
Disallow: /repo/create
Disallow: /dashboard/overview
Disallow: /account/password/reset/

User-agent: 008
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

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 Records
3 A records, 31 ms lookup
PASS
3 A records, 31 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 185.166.143.48, 185.166.143.50, 185.166.143.49
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2401:1d80:3210:2:0:bbc:1:df7c, 2401:1d80:3210:1:0:bbc:1:df7c, 2401:1d80:3210::bbc:1:df7c
Info::
4 nameserver(s) configured
Got: ns-445.awsdns-55.com, ns-584.awsdns-09.net, ns-1746.awsdns-26.co.uk, ns-1305.awsdns-35.org
Info::
2 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: 31 ms
Got: 31 ms
A185.166.143.48, 185.166.143.50, 185.166.143.49
AAAA2401:1d80:3210:2:0:bbc:1:df7c, 2401:1d80:3210:1:0:bbc:1:df7c, 2401:1d80:3210::bbc:1:df7c
CNAME
NSns-445.awsdns-55.com, ns-584.awsdns-09.net, ns-1746.awsdns-26.co.uk, ns-1305.awsdns-35.org
MX
10 mxb-001d9801.gslb.pphosted.com
10 mxa-001d9801.gslb.pphosted.com
TXT
google-site-verification=BIhAfAJXWYr-hSVf3rOpm7IIWSX6mA7d0Na7t-GaEwA
google-site-verification=p99sO7SVcXanHfj-NuQZJKocj3_4Hkws2ZNbbieLW1M
_1tb6ruf8jsqqv5hyasqil8wwbby7knz.dcv.digicert.com
status-page-domain-verification=3fbwzqm8vjhr
google-site-verification=oFmSUhmR77qRC-e8T1kL-eaO7pvT8XUmpw1G0p-lWqM
atlassian-domain-verification=ZRphniOpyvhHV76mRmxnLkHJVrKnbeOIxmhbxb8PF6AarX0Fyp...
SPF v=spf1 ip4:167.89.90.3/32 ip4:167.89.37.79/32 ip4:167.89.38.16/32 ip4:167.89.38....
facebook-domain-verification=84vhrka086if54vvfvdk2ezuvfdwyq
_kc0m4lhl1awr95c7d38tvu102h1x8jf.dcv.digicert.com
google-site-verification=QWfM0kROcuH3GIqpbpGM-jg3ajJyj4Ie5t_LZisV6E0
google-site-verification=X2bEMlmrK-ok6sdGW5j0jsTGCV7IqlqYQxVTV9MQngg
CAALookup not available with standard resolver
Resolved in 31 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://bitbucket.org

https://bitbucket.org

167 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bitbucket.org200167 msHTTP/1.1AtlassianEdge
A+
IPv6 Readiness
IPv6 reachable (34 ms)
PASS
IPv6 reachable (34 ms)
Info::
IPv6 is configured and reachable at 2401:1d80:3210:2:0:bbc:1:df7c, 2401:1d80:3210:1:0:bbc:1:df7c, 2401:1d80:3210::bbc:1:df7c
Got: 34 ms connect
IPv6 Ready
AAAA Records 2401:1d80:3210:2:0:bbc:1:df7c, 2401:1d80:3210:1:0:bbc:1:df7c, 2401:1d80:3210::bbc:1:df7c Connection Reachable (34 ms)
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.bitbucket.org/
200https://bitbucket.org/

Preferred variant: non-www

HTTP → HTTPS

301http://bitbucket.org/ https://bitbucket.org/

Consistent

A+
Domain Intelligence
bitbucket.org — via MarkMonitor Inc., 28 years, 9 months old
PASS
bitbucket.org — via MarkMonitor Inc., 28 years, 9 months old
Info::
Domain registered until Nov 23, 2026 (7 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: MarkMonitor Inc.
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.
Domain expiry

134 days

November 23, 2026

SSL certificate

186 days

Issued by DigiCert Inc

Domain age

28 years, 9 months

Registered November 24, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2401:1d80:3210:2:0:bbc:1:df7c

Registrar

MarkMonitor Inc.

Unlocked 4 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 MarkMonitor Inc.
Created November 24, 1997 (28 years, 9 months ago)
Expires November 23, 2026 (7 months)
Last Updated October 27, 2024
Name Servers ns-1305.awsdns-35.org, ns-1746.awsdns-26.co.uk, ns-445.awsdns-55.com, ns-584.awsdns-09.net
DNSSEC Not enabled
Hosting
IP Address 2401:1d80:3210:2:0:bbc:1:df7c
Data source: rdap (0.6s)

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 204 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
34 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
34 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
197 ms
Total Time Total request time from DNS lookup through full response.
204 ms

Connection waterfall

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

Send Feedback