offzone.moscow
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of offzone.moscow
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 |
|---|---|---|
| 2018.offzone.moscow | 2026-06-16 01:25:22.945 | |
| 2019.offzone.moscow | 2026-06-17 21:04:59.872 | |
| 2022.offzone.moscow | 2026-07-17 15:41:27.017 | |
| 2023.offzone.moscow | 2026-06-19 22:55:14.219 | |
| cfp.offzone.moscow | 1970-01-01 00:00:00.000 | |
| offzone.moscow | 2026-06-25 11:02:45.060 | |
| www.offzone.moscow | 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
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 |
|---|---|---|---|
| MX | 60 mx04.bi.zone | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| NS | ns1.offzone.moscow | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| NS | ns8-l2.nic.ru | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| TXT | google-site-verification=07EwAc4iZ-b-cc7zcoszA_8-btZbQn3sYCvPwvoZh-g | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| TXT | v=spf1 mx ip4:185.163.156.7 ip4:185.163.158.165 ip4:185.163.156.59 ip4:188.225.22.15 ip4:92.53.96.19 ip4:185.163.157.50 ip4:185.163.156.10 ip4:185.163.157.14 ip4:195.201.127.55 ip4:45.9.25.159 ip4:94.139.255.151 include:spf.unisender.com include:spf.ms.bi.zone -all | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| NS | ns4-l2.nic.ru | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| MX | 10 mx.ms.bi.zone | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |
| A | 185.163.159.57 | 2026-06-25 11:02:45.060 | 2026-06-25 11:02:45.060 |