yystatic.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of yystatic.com
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
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
Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.
| Subdomain | Resolves to | Last seen |
|---|---|---|
| res.home.yystatic.com | 2026-07-27 05:35:02.908 | |
| res1.home.yystatic.com | 2026-07-27 05:35:02.908 | |
| yyweb.yystatic.com | 2026-07-24 22:35:56.080 | |
| earn.yystatic.com | 2026-07-24 22:35:56.080 | |
| earn1.yystatic.com | 2026-07-24 22:35:56.080 | |
| ent.yystatic.com | 2026-07-24 22:35:56.080 | |
| ys.yystatic.com | 2026-07-24 22:35:56.080 | |
| web.yystatic.com | 2026-07-15 23:48:16.543 | |
| web1.yystatic.com | 2026-07-15 23:48:16.543 | |
| web2.yystatic.com | 2026-07-15 23:48:16.543 | |
| jy.yystatic.com | 2026-05-26 15:02:14.080 | |
| res0.3g.yystatic.com | 2026-07-24 22:35:56.080 | |
| web3.yystatic.com | 2026-07-15 23:48:16.543 | |
| res.3g.yystatic.com | 2026-07-24 22:35:56.080 | |
| page-res.yystatic.com | 2026-05-26 15:02:14.080 | |
| res.m.yystatic.com | 2026-07-24 22:35:56.080 | |
| res.interfaces.yystatic.com | 2026-07-24 22:35:56.080 | |
| 3g.yystatic.com | 2026-07-28 11:17:57.317 | |
| act.m.yystatic.com | 1970-01-01 00:00:00.000 | |
| act1.m.yystatic.com | 1970-01-01 00:00:00.000 | |
| assets.yystatic.com | 1970-01-01 00:00:00.000 | |
| cdn-a.yystatic.com | 1970-01-01 00:00:00.000 | |
| dl1.vip.yystatic.com | 2026-07-24 19:10:21.723 | |
| dl2.vip.yystatic.com | 1970-01-01 00:00:00.000 | |
| dl3.vip.yystatic.com | 1970-01-01 00:00:00.000 | |
| dl4.vip.yystatic.com | 1970-01-01 00:00:00.000 | |
| kxd-res.yystatic.com | 1970-01-01 00:00:00.000 | |
| live.yystatic.com | 1970-01-01 00:00:00.000 | |
| m.yystatic.com | 2026-07-28 11:17:57.317 | |
| res.co.yystatic.com | 1970-01-01 00:00:00.000 | |
| res0.1931.yystatic.com | 1970-01-01 00:00:00.000 | |
| res0.m.yystatic.com | 1970-01-01 00:00:00.000 | |
| res1.1931.yystatic.com | 1970-01-01 00:00:00.000 | |
| res2.1931.yystatic.com | 1970-01-01 00:00:00.000 | |
| s-yijian.yystatic.com | 1970-01-01 00:00:00.000 | |
| s1-yijian.yystatic.com | 1970-01-01 00:00:00.000 | |
| xyx.yystatic.com | 1970-01-01 00:00:00.000 | |
| ys1.yystatic.com | 1970-01-01 00:00:00.000 | |
| ys2.yystatic.com | 1970-01-01 00:00:00.000 | |
| yystatic.com | 2026-07-28 11:17:57.317 |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
IPs Citing This Domain
No citing IPs found yet
As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.
Origin / IP-Leak
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.
| Origin IP | Origin ASN | CDN ASN | Confidence | Reasoning |
|---|---|---|---|---|
| 221.228.202.164 | AS138950 | AS13335 | 95% | cert 3b737620… served by 221.228.202.164 (AS138950) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 221.228.104.233 | AS138950 | AS13335 | 95% | cert 3b737620… served by 221.228.104.233 (AS138950) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 112.25.94.85 | AS56046 | AS13335 | 95% | cert 4bb471d0… served by 112.25.94.85 (AS56046) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 125.94.240.64 | AS4134 | AS13335 | 95% | cert 3b737620… served by 125.94.240.64 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 123.125.184.137 | AS4808 | AS13335 | 95% | cert 3b737620… served by 123.125.184.137 (AS4808) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 123.125.184.147 | AS4808 | AS13335 | 95% | cert 3b737620… served by 123.125.184.147 (AS4808) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 183.36.121.76 | AS4134 | AS13335 | 95% | cert 3b737620… served by 183.36.121.76 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 121.11.218.216 | AS4134 | AS45102 | 95% | cert fe71b3ab… served by 121.11.218.216 (AS4134) carries SAN web3.yystatic.com which currently resolves through Alibaba (AS45102) at 47.242.124.51, 240e:e9:5005:11fe::15, 240e:97d:2000:701:fe::25, 240b:4001:f10::155 |
| 218.98.23.29 | AS4837 | AS13335 | 95% | cert af54235f… served by 218.98.23.29 (AS4837) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 125.94.245.163 | AS4134 | AS13335 | 95% | cert af54235f… served by 125.94.245.163 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 112.25.94.87 | AS56046 | AS13335 | 95% | cert af54235f… served by 112.25.94.87 (AS56046) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 122.193.205.136 | AS140716 | AS13335 | 95% | cert af54235f… served by 122.193.205.136 (AS140716) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 122.97.255.32 | AS4837 | AS13335 | 95% | cert af54235f… served by 122.97.255.32 (AS4837) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 36.110.128.175 | AS23724 | AS13335 | 95% | cert af54235f… served by 36.110.128.175 (AS23724) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 113.108.82.187 | AS4134 | AS13335 | 95% | cert af54235f… served by 113.108.82.187 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 120.197.132.123 | AS56040 | AS13335 | 95% | cert af54235f… served by 120.197.132.123 (AS56040) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 106.38.197.42 | AS23724 | AS13335 | 95% | cert af54235f… served by 106.38.197.42 (AS23724) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 112.25.79.163 | AS56046 | AS13335 | 95% | cert 4bb471d0… served by 112.25.79.163 (AS56046) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 120.241.148.228 | AS9808 | AS13335 | 95% | cert af54235f… served by 120.241.148.228 (AS9808) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 120.232.148.109 | AS9808 | AS13335 | 95% | cert af54235f… served by 120.232.148.109 (AS9808) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 183.36.121.76 | AS4134 | AS13335 | 95% | cert af54235f… served by 183.36.121.76 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 163.177.75.123 | AS135061 | AS13335 | 95% | cert af54235f… served by 163.177.75.123 (AS135061) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 113.108.82.146 | AS4134 | AS13335 | 95% | cert af54235f… served by 113.108.82.146 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 163.177.75.122 | AS135061 | AS13335 | 95% | cert af54235f… served by 163.177.75.122 (AS135061) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
| 183.2.128.171 | AS4134 | AS13335 | 95% | cert 583103f0… served by 183.2.128.171 (AS4134) carries SAN m.yystatic.com which currently resolves through Cloudflare (AS13335) at 1.1.1.1 |
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.