Domain

4game.ru

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

DNS Check HTTP Check Run Full Scan .ru TLD

Run a live full scan of 4game.ru

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

A/AAAA targets

Subdomains

CT + scan + body

Record Types

seen in DNS

Observed Certs

in our scans

DNS Records

5.63.131.34

AAAA

—

10 relay1-ti.msk.inn.ru, 10 relay2-ti.msk.inn.ru, 20 smtp-relay1-lc.lux.inn.eu, 20 smtp-relay2-lc.lux.inn.eu

ns1.4game.ru, ns2.4game.ru, ns4.inn.ru, ns5.inn.ru

TXT

_globalsign-domain-verification=DGJuUy-IFUapyxHSJT3fnP7XwcUJBi7p2c_-aU05Gg, google-site-verification=Vces4ZGCGyd46jfjthfuS5OIsEQvDA102G9V51ytBhw, mailru-verification: 2cbc3c4c6cff3624, v=spf1 ip4:109.105.128.0/19 ip4:185.47.158.128/29 ip4:5.63.131.128/28 ~all

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.

Subdomain	Resolves to	Last seen
4game.ru	5.63.131.34	2026-07-20 10:20:30.988
autodiscover.gsru-client-log.4game.ru		1970-01-01 00:00:00.000
gsru-client-log.4game.ru	109.105.144.64	2026-06-18 03:17:54.405
mail.gsru-client-log.4game.ru		1970-01-01 00:00:00.000
owa.gsru-client-log.4game.ru		1970-01-01 00:00:00.000
www.gsru-client-log.4game.ru		1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

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

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.