Domain

api.weibo.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of api.weibo.com

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

36.51.224.123, 36.51.224.126

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.

104.194.71.133:443 href · ×2

182.92.4.50:443 href · ×2

47.100.28.162:443 href · ×2

120.55.194.117:443 href · ×2

123.57.255.141:80 href · ×2

149.248.2.30:443 href · ×2

81.70.117.200:443 href · ×2

82.157.37.104:443 href · ×2

101.37.179.30:443 href · ×2

207.56.224.115:443 href · ×2

49.235.95.82:443 href · ×1

47.102.210.241:443 href · ×1

139.224.35.238:443 href · ×1

62.234.12.43:443 href · ×1

123.57.53.61:443 href · ×1

39.103.198.101:443 href · ×1

122.51.93.252:443 href · ×1

8.218.112.210:443 href · ×1

39.101.179.44:443 href · ×1

47.99.75.106:80 href · ×1

47.95.212.111:80 href · ×1

223.4.117.83:80 href · ×1

155.248.211.96:443 href · ×1

62.234.17.12:8080 href · ×1

43.133.26.199:443 href · ×1

43.163.72.219:443 href · ×1

123.56.108.27:80 href · ×1

114.132.214.21:80 href · ×1

8.148.179.140:443 href · ×1

43.142.94.72:443 href · ×1

66.94.126.154:443 href · ×1

115.190.233.32:443 href · ×1

175.24.234.35:443 href · ×1

103.84.89.184:443 href · ×1

39.106.155.221:443 href · ×1

154.17.236.31:443 href · ×1

124.221.59.161:443 href · ×1

149.88.72.61:443 href · ×1

39.106.224.103:443 href · ×1

83.229.122.79:443 href · ×1

23.185.200.189:443 href · ×1

192.129.232.188:443 href · ×1

149.88.85.183:443 href · ×1

47.108.211.216:443 href · ×1

47.76.59.182:443 href · ×1

38.22.95.2:443 href · ×1

165.99.43.52:443 href · ×1

47.121.137.72:443 href · ×1

192.131.142.28:443 href · ×1

150.109.235.72:443 href · ×1

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

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type	Value	First seen	Last seen
A	36.51.224.123	2026-05-25 21:56:50.553	2026-07-28 19:39:40.097
A	36.51.224.126	2026-05-25 21:56:50.553	2026-07-28 19:39:40.097