iroh.computer
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of iroh.computer
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 |
|---|---|---|
| perf.iroh.computer | 2026-05-27 13:03:34.292 | |
| sh.iroh.computer | 2026-06-04 08:08:23.360 | |
| docs.iroh.computer | 2026-07-27 20:51:25.313 | |
| staging.n0des.iroh.computer | 2026-06-15 18:55:38.313 | |
| ips.iroh.computer | 1970-01-01 00:00:00.000 | |
| iroh.computer | 2026-07-25 11:28:26.811 | |
| n0des.iroh.computer | 1970-01-01 00:00:00.000 | |
| vorc.iroh.computer | 2026-06-04 07:26:17.250 | |
| www.iroh.computer | 2026-06-01 10:37:48.472 |
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.
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
Domain timeline pending
Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.