IP Address IPv4

203.55.131.3

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

Ping from 65 Nodes HTTP from 65 Nodes Run Full Scan

Run a live full scan of 203.55.131.3

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

ASN

—

Not yet attributed

Country

—

GeoIP pending

Reverse DNS

—

PTR

Open Ports

—

Last scan

Autonomous System

ASN

—

AS Name

—

AS Type

—

RIR

ARIN

Allocated

2024-04-18

Allocation status

Allocated

Geolocation

Country

—

Continent

—

Source

MaxMind GeoLite2

Reverse DNS

PTR

—

Last seen

—

Network

Prefix

—

RPKI

—

Open Ports

Port-scan data not yet ingested

Open-port and banner-grab data from our scan layer will appear here. World-sweep covers all IPv4 over time — this host may be in a /8 we haven't reached yet.

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

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-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.

Run Ping check

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.

Honeypot Activity

Recurring

This IP hit our honeypot sensors 16 times in the last 90 days — unsolicited connections to services we never advertise, a strong scanner / brute-force signal.

First seen 2026-06-14 17:27:40 Last seen 2026-07-28 22:36:46 Active days 3 Protocols mssql, mysql, dns, https Ports 443, 3306, 1433, 53 JA4 t13i3111h2_e8f1e7e78f70_b26ce05bbdd6

Time	Port	Proto	Event	Credentials / payload
2026-07-28 22:36:46	53	dns	udp_probe	. ...........www.google.com.....
2026-07-23 03:25:02	1433	mssql	payload	474554202f20485454502f312e310d0a486f73743a203138352e3234352e36322e363a313433330d0a557365722d4167656e743a204d6f7a696c6c612f352e30202857696e646f7773204e542031302e303b2057696e36343b2078363429204170706c65
2026-07-23 03:24:52	1433	mssql	connect
2026-07-23 03:09:20	1433	mssql	payload	16030100ec010000e8030393f8a61ee5de75b4289b8e9a34f84ee68d284a0e690b66b7138015e80dc3c42820eff6550a3c43e68fe7e347d50dac266b15be5975be899ff4d0de4e0c1a7e6ca400209a9a130113021303c02bc02fc02cc030cca9cca8c013
2026-07-23 03:09:10	1433	mssql	connect
2026-07-23 02:53:58	1433	mssql	payload	1201002f0000020000001a00060100200001020021000103002200040400260001ff00000000000001000000000000
2026-07-23 02:53:48	1433	mssql	connect
2026-07-12 10:02:50	3306	mysql	connect
2026-07-12 07:38:31	443	https	http_request	GET /favicon.ico host: 185.245.62.6 user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 accept: /
2026-07-12 07:38:31	443	https	tls_clienthello	ja3=78f0dc5ac5b19daf131a133cfdee9691 ja4=t13i3111h2_e8f1e7e78f70_b26ce05bbdd6
2026-07-12 07:37:26	443	https	http_request	GET / host: 185.245.62.6 user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 accept: / accept-encoding: gzip
2026-07-12 07:37:26	443	https	tls_clienthello	ja3=02fc9e6401d2c8c1bf8f91bd21b8e17e ja4=t13i150900_8daaf6152771_18e8a06d9b2d
2026-06-14 17:27:59	443	https	http_request	GET /favicon.ico host: 185.245.62.6 user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 accept: /
2026-06-14 17:27:59	443	https	tls_clienthello	ja3=78f0dc5ac5b19daf131a133cfdee9691 ja4=t13i3111h2_e8f1e7e78f70_b26ce05bbdd6
2026-06-14 17:27:41	443	https	http_request	GET / host: 185.245.62.6 user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 accept: / accept-encoding: gzip
2026-06-14 17:27:40	443	https	tls_clienthello	ja3=02fc9e6401d2c8c1bf8f91bd21b8e17e ja4=t13i150900_8daaf6152771_18e8a06d9b2d

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

Historical change-log pending

ASN changes, prefix re-allocations, cert rotations, port-state diffs over months — accumulates as our archives grow.