bit.ly was registered with Libyan Spider Network (int) on 17 May 2008 and is hosted on AS396982 Google LLC in United States of America. Its SSL certificate from Let's Encrypt expired on 15 Jun 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
The WOT community hasn't rated this domain yet.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is bit.ly’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| India | 26.8% | 459,064,780 | 7% | 99.9% |
| United States | 9.7% | 165,604,258 | 63% | 99.4% |
| Indonesia | 9.3% | 159,223,456 | 13% | 99.9% |
| Brazil | 4.1% | 69,210,770 | 54% | 99.5% |
| Thailand | 4% | 67,942,938 | 6% | 99.9% |
3 technologies detected across 3 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address bit.ly resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| bit.ly | 67.199.248.10 | 109 |
| bit.ly | 67.199.248.11 | 109 |
| Host | Mail server | TTL |
|---|---|---|
| bit.ly | 10 aspmx.l.google.com | 363 |
| bit.ly | 20 alt1.aspmx.l.google.com | 363 |
| bit.ly | 20 alt2.aspmx.l.google.com | 363 |
| bit.ly | 30 aspmx2.googlemail.com | 363 |
| bit.ly | 30 aspmx3.googlemail.com | 363 |
| Host | Name server | TTL |
|---|---|---|
| bit.ly | ns-1372.awsdns-43.org | 18908 |
| bit.ly | ns-1766.awsdns-28.co.uk | 18908 |
| bit.ly | ns-276.awsdns-34.com | 18908 |
| bit.ly | ns-705.awsdns-24.net | 18908 |
| bit.ly | ns-cloud-c1.googledomains.com | 18908 |
| bit.ly | ns-cloud-c2.googledomains.com | 18908 |
| bit.ly | ns-cloud-c3.googledomains.com | 18908 |
| bit.ly | ns-cloud-c4.googledomains.com | 18908 |
| Host | Text | TTL |
|---|---|---|
| bit.ly | "2205ECE8B9" | 3600 |
| bit.ly | "9ab819f3-2495-4611-856e-26a99cb9e4ba" | 3600 |
| bit.ly | "apple-domain-verification=6YYbatV9m7YWHrdw" | 3600 |
| bit.ly | "atlassian-domain-verification=Th+HeZjMKa3QxX9JqLt67kxMrAsEfB9gz51iuPZYjYbveQXnMLmOBQtqalJXXWmO" | 3600 |
| bit.ly | "google-site-verification: zhEwFAQvtUWYInQtt81loDiZmomsEmkAbuRsSSxk1YI" | 3600 |
| bit.ly | "miro-verification=fac1aeff65bb8e30ec8efd62a6ba02f2ce19a82c" | 3600 |
| bit.ly | "v=spf1 include:_spf.google.com include:_spf.salesforce.com include:mailgun.org -all" | 3600 |
| bit.ly | "yandex-verification: 41b3ec866726729d" | 3600 |
| Host | Policy | TTL |
|---|---|---|
| bit.ly | 0 iodef mailto:[email protected] | 3600 |
| bit.ly | 0 issue digicert.com | 3600 |
| bit.ly | 0 issuewild \; | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| bit.ly | ns-1372.awsdns-43.org awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
No reviews yet. Used bit.ly? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
Its SSL certificate expired on 15 Jun 2024. See Security →
bit.ly is registered through Libyan Spider Network (int). The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expires on 17 May 2032 — in 5 years. See Overview →
bit.ly was registered on 17 May 2008, making it 18 years old. See Overview →
bit.ly is served from 2 IP addresses, mainly on AS396982 Google LLC in United States of America. See Hosting →
We detected 3 technologies, including Google Analytics, WordPress and jQuery. See Built with →
Raw registry data for bit.ly. May be redacted by privacy services.
Domain Name: bit.ly Registry Domain ID: 24501-CoCCA Registry WHOIS Server: whois.nic.ly Updated Date: 2022-04-18T03:12:18.153Z Creation Date: 2008-05-17T22:00:00.0Z Registry Expiry Date: 2032-05-17T22:00:00.0Z Registrar Registration Expiration Date: 2032-05-17T22:00:00.0Z Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Registry Registrant ID: lOz5p-JSJz7 Registrant Name: bitly operations Registrant Organization: Bitly, Inc. Registrant Street: DPT 5006 Registrant Street: 601 W 26th St, 3rd Floor, STE 357 Registrant City: New York Registrant State/Province: NY Registrant Postal Code: 10001 Registrant Country: US Registrant Phone: +64.66785610 Registrant Email: [email protected] Registrar: Libyan Spider Network (int) Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.8448469791 Name Server: ns-1372.awsdns-43.org Name Server: ns-705.awsdns-24.net Name Server: ns-cloud-c1.googledomains.com Name Server: ns-cloud-c2.googledomains.com Name Server: ns-cloud-c3.googledomains.com DNSSEC: unsigned >>> Last update of WHOIS database: 2024-05-08T02:51:53.100Z <<< For more information on EPP status codes, please visit https://icann.org/epp TERMS OF USE: You are not authorized to access or query our WHOIS database through the use of electronic processes that are high-volume and automated. This WHOIS database is provided by as a service to the internet community. The data is for information purposes only. We do not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: You agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes. The compilation, repackaging, dissemination or other use of this data is expressly prohibited.
The first response from http://www.bit.ly, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with bit.ly. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.