Check-Host.cc

Domain

web.telegram.org

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

Run a live full scan of web.telegram.org

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
149.154.167.99
AAAA
2001:67c:4e8:f004::9
MX
NS
TXT
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.

18.140.94.41:80 href · ×8
116.203.203.206:443 href · ×6
103.139.1.28:443 href · ×6
88.193.131.13:443 href · ×4
209.99.184.87:443 href · ×4
213.139.210.179:443 href · ×4
52.76.173.143:443 href · ×3
62.192.149.22:443 href · ×3
38.127.216.62:443 href · ×3
104.248.33.136:443 href · ×3
216.107.138.45:80 href · ×3
103.39.79.205:443 href · ×3
148.153.116.150:443 href · ×3
146.103.45.249:443 href · ×3
213.171.15.253:443 href · ×3
154.18.239.189:443 href · ×3
43.155.214.159:443 href · ×3
185.120.59.167:443 href · ×3
188.40.90.163:443 href · ×3
83.97.111.55:80 href · ×3
137.220.156.221:80 href · ×3
188.40.90.163:80 href · ×3
142.91.105.158:443 href · ×3
27.124.45.126:443 href · ×3
185.243.99.14:80 href · ×3
1.14.171.49:443 href · ×3
192.163.161.107:443 href · ×3
45.76.244.146:443 href · ×2
88.99.190.249:443 href · ×2
195.133.1.66:443 href · ×2
154.37.153.252:443 href · ×2
121.5.38.2:443 href · ×2
159.54.140.35:443 href · ×2
209.159.148.189:443 href · ×2
185.227.144.120:443 href · ×2
95.217.213.198:443 href · ×2
51.68.127.103:80 href · ×2
188.226.141.75:443 href · ×2
31.57.44.28:443 href · ×2
45.12.114.228:80 href · ×2
89.167.56.154:80 href · ×2
47.79.145.139:443 href · ×2
52.170.56.153:443 href · ×2
185.69.154.93:443 href · ×2
89.104.71.188:443 href · ×2
35.220.155.236:8008 href · ×2
45.32.111.191:80 href · ×2
95.58.194.53:443 href · ×2
83.220.171.156:443 href · ×2
193.42.38.59:443 href · ×2

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.

c71c05a233a3189e… google · argon2026h2
Subject: *.web.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.web.telegram.org, web.telegram.org
Valid: 2025-08-29 16:48:47 → 2026-09-30 16:48:47

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
AAAA 2001:67c:4e8:f004::9 2026-05-25 22:02:50.525 2026-07-28 20:47:52.650
A 149.154.167.99 2026-05-25 22:02:50.525 2026-07-28 20:47:52.650