149.126.76.155
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of 149.126.76.155
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 |
|---|---|---|---|---|
| 80 | tcp | http | — | 2026-05-26 02:04:18.000 |
| 88 | tcp | kerberos | — | 2026-06-14 03:13:47.000 |
| 110 | tcp | pop3 | — | 2026-05-26 12:00:13.000 |
| 953 | tcp | — | — | 2026-06-16 16:31:49.000 |
| 1024 | tcp | — | — | 2026-06-20 12:35:57.000 |
| 1352 | tcp | — | — | 2026-07-19 22:01:26.000 |
| 1521 | tcp | oracle | — | 2026-07-18 12:56:55.000 |
| 1720 | tcp | — | — | 2026-07-18 10:57:13.000 |
| 2082 | tcp | — | — | 2026-06-21 16:27:22.000 |
| 2095 | tcp | — | — | 2026-06-17 01:24:57.000 |
| 2096 | tcp | — | — | 2026-06-21 02:31:05.000 |
| 2701 | tcp | — | — | 2026-06-15 19:39:21.000 |
| 3306 | tcp | mysql | — | 2026-06-23 23:28:42.000 |
| 4443 | tcp | — | — | 2026-06-22 06:33:33.000 |
| 5005 | tcp | — | — | 2026-06-15 23:18:05.000 |
| 5222 | tcp | — | — | 2026-06-22 01:03:41.000 |
| 5500 | tcp | — | — | 2026-06-19 15:07:50.000 |
| 5672 | tcp | amqp | — | 2026-06-22 12:15:55.000 |
| 5800 | tcp | — | — | 2026-06-15 04:24:22.000 |
| 8081 | tcp | — | — | 2026-06-07 19:45:14.000 |
| 8083 | tcp | — | — | 2026-06-18 10:13:26.000 |
| 8089 | tcp | — | — | 2026-07-21 15:36:04.000 |
| 8118 | tcp | — | — | 2026-07-18 12:17:12.000 |
| 8530 | tcp | — | — | 2026-06-07 05:10:45.000 |
| 18091 | tcp | — | — | 2026-06-19 04:55:13.000 |
| 50050 | tcp | — | — | 2026-06-14 20:37:36.000 |
TLS Certificates
TLS certificate observations pending
Once our scan layer captures a TLS cert from this IP, certificate chain, JARM and JA4S fingerprints will appear here.
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.
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.
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
No DNS-confirmed domains yet
We cross-reference body-cited domains against our DNS resolver records. Confirmations appear here once both sides have data for the same name.
External References
No external references found yet
As HTML bodies get banner-grabbed, references to external domains land here.
History
The full change-log (ASN moves, cert rotations, port-state diffs) accumulates as our archives grow.