Domain

bit.ly

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .ly TLD

Run a live full scan of bit.ly

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now

Hosting IPs

—

A/AAAA targets

Subdomains

—

CT + scan + body

Record Types

—

seen in DNS

Observed Certs

—

in our scans

DNS Records

—

AAAA

—

TXT

—

CNAME

—

CAA

—

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

159.223.69.83:443 href · ×185

168.144.35.71:443 href · ×181

143.198.222.98:443 href · ×171

157.245.157.242:443 href · ×171

139.59.126.151:443 href · ×171

178.128.102.76:443 href · ×171

159.89.197.11:443 href · ×171

167.172.89.216:443 href · ×171

157.230.246.154:443 href · ×171

139.59.120.76:443 href · ×171

159.65.230.253:80 href · ×84

67.205.139.128:80 href · ×84

66.39.149.233:443 href · ×64

157.7.131.178:80 href · ×50

178.128.209.86:443 href · ×48

3.39.14.21:80 href · ×47

45.76.219.70:80 href · ×40

91.189.115.83:80 href · ×30

35.201.219.148:443 href · ×28

61.64.52.156:443 href · ×27

125.229.46.69:80 href · ×27

52.74.219.215:80 href · ×24

18.207.141.154:443 href · ×22

13.213.204.71:443 href · ×19

139.59.95.236:80 href · ×18

66.39.39.84:80 href · ×18

134.122.42.71:443 href · ×18

172.233.152.65:80 href · ×18

34.201.240.96:80 href · ×18

158.195.89.58:443 href · ×17

158.195.89.58:80 href · ×17

207.154.216.181:443 href · ×17

50.16.85.11:443 href · ×17

45.79.159.115:443 href · ×16

23.253.78.108:80 href · ×16

202.28.77.130:443 href · ×16

35.167.186.164:443 href · ×16

35.167.186.164:80 href · ×16

159.198.76.173:443 href · ×16

185.245.98.190:443 href · ×16

159.65.0.201:443 href · ×16

192.64.116.231:443 href · ×16

104.131.214.213:443 href · ×16

178.128.81.151:443 href · ×14

157.230.41.185:443 href · ×14

163.43.127.102:80 href · ×14

157.230.43.29:443 href · ×14

216.222.199.82:443 href · ×14

159.198.66.232:443 href · ×14

152.42.198.25:443 href · ×14

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.