Check-Host.cc

Domain

static.oneinstack.com

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

Run a live full scan of static.oneinstack.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
6
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
in our scans

DNS Records

A
104.21.3.237, 172.67.131.85
AAAA
2606:4700:3033::ac43:8355, 2606:4700:3034::6815:3ed, 2606:4700:3034::ac43:8355, 2606:4700:3037::6815:3ed
MX
NS
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.

139.224.35.48:80 href · ×36
49.50.175.123:80 href · ×36
8.134.179.255:80 href · ×36
182.92.215.19:80 href · ×27
193.123.246.103:80 href · ×24
47.90.206.211:80 href · ×24
42.192.192.149:80 href · ×24
101.37.170.32:80 href · ×24
124.71.220.151:80 href · ×24
124.221.237.121:80 href · ×24
149.129.53.79:80 href · ×24
202.55.82.243:8080 href · ×24
98.126.235.100:80 href · ×24
47.74.7.197:80 href · ×24
165.1.66.51:80 href · ×24
101.37.35.109:8080 href · ×24
140.238.61.0:80 href · ×24
123.57.248.233:80 href · ×24
101.201.239.106:80 href · ×24
124.71.131.24:80 href · ×24
13.236.233.10:443 href · ×24
47.103.219.28:80 href · ×24
139.9.119.47:80 href · ×24
132.232.191.251:80 href · ×24
101.33.205.89:80 href · ×24
47.102.113.101:80 href · ×24
140.238.3.220:80 href · ×24
47.100.61.212:80 href · ×24
45.58.52.89:80 href · ×24
47.99.104.10:80 href · ×24
47.244.127.126:80 href · ×24
121.196.197.143:443 href · ×24
192.243.118.216:80 href · ×24
152.136.59.35:80 href · ×24
118.31.118.23:443 href · ×24
123.57.103.110:80 href · ×24
18.138.234.54:80 href · ×24
43.138.105.143:80 href · ×24
103.39.231.45:80 href · ×24
111.230.205.185:80 href · ×24
212.107.29.97:80 href · ×24
121.37.161.96:80 href · ×24
159.203.62.99:80 href · ×24
121.37.24.183:80 href · ×24
120.25.84.73:80 href · ×24
54.152.21.227:80 href · ×24
121.41.29.159:80 href · ×24
47.96.10.232:80 href · ×24
47.102.136.153:80 href · ×24
117.72.92.50:80 href · ×24

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
AAAA 2606:4700:3034::ac43:8355 2026-05-25 21:58:50.500 2026-06-23 23:54:32.134
A 104.21.3.237 2026-05-25 21:58:50.500 2026-07-28 20:47:52.650
AAAA 2606:4700:3037::6815:3ed 2026-05-25 21:58:50.500 2026-06-23 23:54:32.134
A 172.67.131.85 2026-05-25 21:58:50.500 2026-07-28 20:47:52.650
AAAA 2606:4700:3033::ac43:8355 2026-07-15 22:21:10.369 2026-07-28 20:47:52.650
AAAA 2606:4700:3034::6815:3ed 2026-07-15 22:21:10.369 2026-07-28 20:47:52.650