Domain
dzen.ru
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of dzen.ru
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
Hosting IPs
—
A/AAAA targets
Subdomains
—
CT + scan + body
Record Types
—
seen in DNS
Observed Certs
—
in our scans
DNS Records
A
185.180.200.2, 5.61.23.39, 83.222.28.15, 95.163.218.220
AAAA
2a00:b4c0:9100:b000::1:b0
MX
10 emx.mail.ru
NS
ns1.mail.ru, ns2.mail.ru
TXT
HARICA-2jAI3HyTrAot8qKQfyk, HARICA-4ADUGCXKniBqOdcUs42, HARICA-TmXYkd9JS0rYRVCUdTP, _globalsign-domain-verification=cH6yooynQIEMCm5q0ZI_zdx1JDUpA3t6tLLCupTaFl, _globalsign-domain-verification=mRLVFszXGRAFQd2B_2oK0ivc9l7b0q5tykxcUPNwH4, google-site-verification=IRlvaJA-WdmbZODuCN7DI_5wWm8CEPfYRdDVhwD_27Q, mailru-verification: 6199e899d08e90d8, v=spf1 redirect=_spf.mail.ru
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
Subdomain enumeration pending
Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: sso-test.sso.dzen.ru
Issuer: YandexInternalCA
SANs: sso-test.sso.dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru
IPs Citing This Domain
Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.
84.252.138.15:443
href · ×87
176.108.245.147:80
href · ×16
176.108.245.147:443
href · ×16
158.160.193.35:443
href · ×14
93.77.184.224:8080
href · ×12
185.241.192.54:443
href · ×10
79.174.82.224:443
href · ×10
79.174.82.224:80
href · ×10
46.19.66.224:8000
href · ×9
195.133.41.245:443
href · ×8
87.242.70.82:443
href · ×8
109.73.206.110:443
href · ×7
178.210.89.10:443
href · ×7
185.207.66.19:443
href · ×7
92.255.108.172:443
href · ×6
195.2.71.141:443
href · ×6
37.1.222.186:80
href · ×6
82.146.54.237:443
href · ×5
80.78.244.122:443
href · ×5
144.31.203.175:443
href · ×5
37.233.81.244:9443
href · ×5
45.128.206.148:443
href · ×4
217.114.0.141:443
href · ×4
89.169.170.169:443
href · ×4
45.8.251.200:443
href · ×4
155.212.224.148:443
href · ×4
185.43.5.108:443
href · ×4
80.87.110.41:443
href · ×4
213.248.43.20:443
href · ×4
194.87.110.220:80
href · ×4
109.236.57.120:443
href · ×4
95.163.236.254:443
href · ×4
45.128.207.33:443
href · ×4
37.77.104.27:443
href · ×4
194.67.92.79:80
href · ×4
95.183.14.4:80
href · ×3
185.9.26.68:8443
href · ×3
87.242.71.108:443
href · ×3
201.51.9.218:443
href · ×3
79.174.95.76:443
href · ×3
178.159.47.152:80
href · ×3
89.111.155.158:443
href · ×3
109.71.247.147:443
href · ×3
89.207.252.109:443
href · ×3
217.12.37.70:443
href · ×3
155.212.216.148:443
href · ×3
147.45.159.113:443
href · ×3
217.114.13.222:443
href · ×3
5.42.104.148:443
href · ×3
217.198.5.158:80
href · ×3
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.
CT-Log Evidence
Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.
43fdd85919676397…
cloudflare · nimbus2026
Subject: *.dzen.ru
Issuer: HARICA DV TLS RSA
SANs: *.dzen.ru, dzen.ru, *.zen.zeta.dzen.ru, zen.zeta.dzen.ru
Valid: 2025-08-06 12:26:59 → 2026-08-06 12:26:59
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.180.200.2 | 2026-05-25 21:30:03.372 | 2026-07-28 20:23:38.809 |
| A | 5.61.23.39 | 2026-05-25 21:30:03.372 | 2026-07-28 20:23:38.809 |
| A | 83.222.28.15 | 2026-05-25 21:30:03.372 | 2026-07-28 20:23:38.809 |
| TXT | yandex-verification: cfa581ef67bd92ea | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | google-site-verification=IRlvaJA-WdmbZODuCN7DI_5wWm8CEPfYRdDVhwD_27Q | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | mailru-verification: 6199e899d08e90d8 | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| NS | ns2.mail.ru | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | v=spf1 redirect=_spf.mail.ru | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | yandex-verification: fdfc71b87280ddfb | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| MX | 10 emx.mail.ru | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | HARICA-2jAI3HyTrAot8qKQfyk | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | _globalsign-domain-verification=mRLVFszXGRAFQd2B_2oK0ivc9l7b0q5tykxcUPNwH4 | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| NS | ns1.mail.ru | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | yandex-verification: 1d9ecd817a647a1f | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | _globalsign-domain-verification=cH6yooynQIEMCm5q0ZI_zdx1JDUpA3t6tLLCupTaFl | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | HARICA-TmXYkd9JS0rYRVCUdTP | 2026-05-25 22:05:29.416 | 2026-07-28 20:23:38.809 |
| TXT | HARICA-4ADUGCXKniBqOdcUs42 | 2026-06-14 22:08:58.337 | 2026-07-28 20:23:38.809 |
| A | 95.163.218.220 | 2026-07-27 12:21:18.087 | 2026-07-28 20:23:38.809 |
| AAAA | 2a00:b4c0:9100:b000::1:b0 | 2026-07-27 12:21:18.087 | 2026-07-28 20:23:38.809 |