Check-Host.cc

Domain

devim.team

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

Run a live full scan of devim.team

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
27
A/AAAA targets
Subdomains
471
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
17
in our scans

DNS Records

A
176.57.66.218
AAAA
MX
10 mx.yandex.net
NS
etta.ns.cloudflare.com, piotr.ns.cloudflare.com
TXT
MS=EDA5B144B3BF70733C3117446FF93745A2670F64, atlassian-domain-verification=pXtmcczm1gWxitlJqm4xfovjTtGahOwpdJdLOAhMD0VgfO0msK3wJ57YbOfCh9aL, google-site-verification=08x2R9QBYs6U3ULI3YJG6DgsDndwCIFj-P6ilmOKOo0, google-site-verification=kPa5LPZMDZwtX4RMphJg3lQ8WY0BOIsURBmsl_B9Ehg, mailru-domain: gOfmuP0O3WquJZ52, mailruverify99466, rm_verify=c0359173f3, v=spf1 ip4:185.147.81.25 include:_spf.yandex.net ~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

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: root@1-prod-hoster-03.devim.team
Issuer: root@1-prod-hoster-03.devim.team
SANs: 1-prod-hoster-03.devim.team, 10.0.11.2/24, 2a00:ab00:300:9be::27/64, 78.155.223.236/29, fe80::1/64, fe80::225:90ff:fe5d:5d3a/64, fe80::225:90ff:fe5d:5d3b/64, fe80::7808:a0ff:fe16:21a1/64, root@1-prod-hoster-03.devim.team

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
TXT mailru-domain: gOfmuP0O3WquJZ52 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT google-site-verification=kPa5LPZMDZwtX4RMphJg3lQ8WY0BOIsURBmsl_B9Ehg 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
MX 10 mx.yandex.net 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
NS etta.ns.cloudflare.com 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
A 176.57.66.218 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT yandex-verification: 9c1e4f4986d916a6 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT atlassian-domain-verification=pXtmcczm1gWxitlJqm4xfovjTtGahOwpdJdLOAhMD0VgfO0msK3wJ57YbOfCh9aL 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
NS piotr.ns.cloudflare.com 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT mailruverify99466 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT MS=EDA5B144B3BF70733C3117446FF93745A2670F64 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT v=spf1 ip4:185.147.81.25 include:_spf.yandex.net ~all 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT google-site-verification=08x2R9QBYs6U3ULI3YJG6DgsDndwCIFj-P6ilmOKOo0 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011
TXT rm_verify=c0359173f3 2026-06-04 21:15:58.011 2026-06-04 21:15:58.011