136.68.0.70
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of 136.68.0.70
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
Autonomous System
Geolocation
Reverse DNS
Network
Open Ports
| Port | Proto | Service | Server | Last seen |
|---|---|---|---|---|
| 49 | tcp | — | — | 2026-06-22 10:14:25.000 |
| 111 | tcp | — | — | 2026-06-15 13:10:59.000 |
| 113 | tcp | — | — | 2026-05-31 08:48:51.000 |
| 139 | tcp | netbios-ssn | — | 2026-06-23 06:13:53.000 |
| 179 | tcp | bgp | — | 2026-06-06 06:41:26.000 |
| 443 | tcp | https | Google Frontend | 2026-07-18 19:49:20.000 |
| 445 | tcp | smb | — | 2026-06-15 03:54:11.000 |
| 464 | tcp | — | — | 2026-06-16 14:05:26.000 |
| 523 | tcp | — | — | 2026-06-22 19:49:00.000 |
| 540 | tcp | — | — | 2026-06-16 19:24:35.000 |
| 554 | tcp | — | — | 2026-06-07 08:18:53.000 |
| 666 | tcp | — | — | 2026-06-14 03:10:35.000 |
| 902 | tcp | — | — | 2026-06-17 19:00:27.000 |
| 1110 | tcp | — | — | 2026-06-18 22:25:52.000 |
| 1352 | tcp | — | — | 2026-06-21 03:08:34.000 |
| 2121 | tcp | — | — | 2026-06-20 08:09:38.000 |
| 3690 | tcp | — | — | 2026-06-21 06:20:23.000 |
| 5004 | tcp | — | — | 2026-06-17 23:09:43.000 |
| 5006 | tcp | — | — | 2026-05-31 10:02:39.000 |
| 5601 | tcp | — | — | 2026-06-21 18:58:49.000 |
| 5985 | tcp | winrm-http | — | 2026-06-21 14:20:51.000 |
| 8082 | tcp | — | — | 2026-05-31 09:31:27.000 |
| 8765 | tcp | — | — | 2026-06-16 06:11:05.000 |
| 9443 | tcp | — | — | 2026-06-15 09:14:26.000 |
| 49153 | tcp | — | — | 2026-06-18 04:12:39.000 |
TLS Certificates
Tech Stack
Wappalyzer fingerprinting pending
HTTP-body analysis identifies web frameworks, CMS platforms, analytics, JS libraries and server-side languages from this host.
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.
No origin-leak candidates for this IP
When this IP serves a TLS cert for a domain that fronts behind a CDN, that domain surfaces here as an origin-leak candidate with a confidence score.
Hosted Domains
2 domains resolve (A-record) to this IP.
Multi-Vantage Check
Reachability accrued passively from real user-triggered checks across our 65+ probe nodes. Run a live check to add fresh data.
No accumulated reachability data yet
Reachability accrues from real user-triggered checks. Trigger a Ping or HTTP check from our 65+ probe nodes to contribute the first data point.
Web Pages
| Port | Page title | Status | Flags |
|---|---|---|---|
| 443 | X.com | 200 |
Threat Intelligence
No threat-intel matches
This IP doesn't appear in any of the feeds we mirror (Tor exits, FireHOL Level 1-3, Spamhaus DROP/EDROP, URLhaus, OpenPhish). Absence here doesn't prove the IP is clean — it just means none of our public-feed sources flag it.
Co-Hosted Domains
Domains this host references in its HTML AND whose DNS A/AAAA record resolves back to this IP — i.e. actually hosted here.
External References
Domains the body links to whose DNS does NOT resolve to this IP — usually CDN assets, embeds, or third-party services. Boilerplate (Google Fonts, jsDelivr, w3.org…) is already filtered.
History
The full change-log (ASN moves, cert rotations, port-state diffs) accumulates as our archives grow.