Check-Host.cc

Domain

e.lanbook.com

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

Run a live full scan of e.lanbook.com

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

A
81.163.20.50
AAAA
MX
50 mx02.nicmail.ru, 51 mx01.nicmail.ru
NS
TXT
201810111942402bs4te4ixx0eykgs530ayijr5p6wtajsu67bx5tm6uuawbcqhm, _globalsign-domain-verification=0Cf_IhH0I3xBu8CR1_kPYp3_mhLW_GK48LImYzpyv1, _globalsign-domain-verification=0IpxazPHW6mA46Gb2OQP0TF6Bejn7Y1LtKcLFi2Gr5, v=spf1 a mx ip4:77.223.124.242 ip4:77.223.124.243 ip4:77.223.124.244 ip4:81.163.20.50 ~all, yandex-verification: df9aed622501e921
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

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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

81.90.213.162:80 href · ×2
93.88.136.19:80 href · ×2
77.246.145.60:80 href · ×2
80.237.110.109:443 href · ×2
193.238.110.226:443 href · ×2
62.182.30.22:80 href · ×1

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 v=spf1 a mx ip4:77.223.124.242 ip4:77.223.124.243 ip4:77.223.124.244 ip4:81.163.20.50 ~all 2026-05-27 08:32:15.694 2026-07-26 20:11:53.429
TXT 201810111942402bs4te4ixx0eykgs530ayijr5p6wtajsu67bx5tm6uuawbcqhm 2026-05-27 08:32:15.694 2026-07-26 20:11:53.429
TXT _globalsign-domain-verification=0Cf_IhH0I3xBu8CR1_kPYp3_mhLW_GK48LImYzpyv1 2026-05-27 08:32:15.694 2026-06-21 11:31:26.238
MX 51 mx01.nicmail.ru 2026-05-27 08:32:15.694 2026-07-26 20:11:53.429
A 81.163.20.50 2026-05-27 08:32:15.694 2026-07-26 20:11:53.429
MX 50 mx02.nicmail.ru 2026-05-27 08:32:15.694 2026-07-26 20:11:53.429
TXT yandex-verification: df9aed622501e921 2026-05-27 08:32:15.694 2026-07-26 20:11:53.429
TXT _globalsign-domain-verification=0IpxazPHW6mA46Gb2OQP0TF6Bejn7Y1LtKcLFi2Gr5 2026-07-23 09:10:34.818 2026-07-26 20:11:53.429