Check-Host.cc

Domain

rt.gy

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

Run a live full scan of rt.gy

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
72
A/AAAA targets
Subdomains
45
CT + scan + body
Record Types
3
seen in DNS
Observed Certs
9
in our scans

DNS Records

A
104.21.57.117, 172.67.190.89, 185.225.112.105
AAAA
2606:4700:3030::ac43:be59, 2606:4700:3034::6815:3975
MX
NS
melissa.ns.cloudflare.com, nitin.ns.cloudflare.com
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

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: p4.main.stream.rt.gy
Issuer: YR2
SANs: p4.main.stream.rt.gy, p4.stream.cdn.moi
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: p5.main.stream.rt.gy
Issuer: YR2
SANs: p5.main.stream.rt.gy, p5.stream.cdn.moi
Subject: p5.main.stream.rt.gy
Issuer: YR2
SANs: p5.main.stream.rt.gy, p5.stream.cdn.moi
Subject: catch.main.stream.rt.gy
Issuer: YR1
SANs: catch.main.stream.rt.gy, catch.stream.cdn.moi
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: p5.main.stream.rt.gy
Issuer: YR2
SANs: p5.main.stream.rt.gy, p5.stream.cdn.moi
Subject: p3.main.stream.rt.gy
Issuer: YR2
SANs: p3.main.stream.rt.gy, p3.stream.cdn.moi
Subject: p4.main.stream.rt.gy
Issuer: YR2
SANs: p4.main.stream.rt.gy, p4.stream.cdn.moi
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: p4.main.stream.rt.gy
Issuer: YR2
SANs: p4.main.stream.rt.gy, p4.stream.cdn.moi
Subject: p3.main.stream.rt.gy
Issuer: YR2
SANs: p3.main.stream.rt.gy, p3.stream.cdn.moi
Subject: p4.main.stream.rt.gy
Issuer: YR2
SANs: p4.main.stream.rt.gy, p4.stream.cdn.moi
Subject: catch.main.stream.rt.gy
Issuer: YR1
SANs: catch.main.stream.rt.gy, catch.stream.cdn.moi
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: p1.main.stream.rt.gy
Issuer: YR1
SANs: p1.main.stream.rt.gy, p1.stream.cdn.moi
Subject: p2.main.stream.rt.gy
Issuer: YR1
SANs: p2.main.stream.rt.gy, p2.stream.cdn.moi
Subject: p2.main.stream.rt.gy
Issuer: YR1
SANs: p2.main.stream.rt.gy, p2.stream.cdn.moi
Subject: port.gyermelyi.hu
Issuer: YR2
SANs: port.gyermelyi.hu, port.holding.gyermelyi.hu
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: yz.gl
Issuer: YR1
SANs: rt.gy, sy.hn, yz.gl
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: p2.main.stream.rt.gy
Issuer: YR1
SANs: p2.main.stream.rt.gy, p2.stream.cdn.moi
Subject: p3.main.stream.rt.gy
Issuer: YR2
SANs: p3.main.stream.rt.gy, p3.stream.cdn.moi
Subject: p6.main.stream.rt.gy
Issuer: YR2
SANs: p6.main.stream.rt.gy, p6.stream.cdn.moi
Subject: catch.main.stream.rt.gy
Issuer: YR1
SANs: catch.main.stream.rt.gy, catch.stream.cdn.moi
Subject: p1.main.stream.rt.gy
Issuer: YR1
SANs: p1.main.stream.rt.gy, p1.stream.cdn.moi
Subject: p3.main.stream.rt.gy
Issuer: YR2
SANs: p3.main.stream.rt.gy, p3.stream.cdn.moi
Subject: p5.main.stream.rt.gy
Issuer: YR2
SANs: p5.main.stream.rt.gy, p5.stream.cdn.moi

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

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
A 185.225.112.105 2026-05-26 03:46:08.458 2026-05-27 07:21:42.379
NS melissa.ns.cloudflare.com 2026-05-26 03:46:08.458 2026-07-22 22:53:08.725
NS nitin.ns.cloudflare.com 2026-05-26 03:46:08.458 2026-07-22 22:53:08.725
A 104.21.57.117 2026-06-22 09:42:15.482 2026-07-22 22:53:08.725
AAAA 2606:4700:3034::6815:3975 2026-06-22 09:42:15.482 2026-07-22 22:53:08.725
AAAA 2606:4700:3030::ac43:be59 2026-06-22 09:42:15.482 2026-07-22 22:53:08.725
A 172.67.190.89 2026-06-22 09:42:15.482 2026-07-22 22:53:08.725