Check-Host.cc

Domain

core.telegram.org

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

Run a live full scan of core.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
2
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
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

Subject: core.telegram.org
Issuer: core.telegram.org
SANs: core.telegram.org

IPs Citing This Domain

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

176.12.76.55:443 href · ×8
43.103.6.221:443 href · ×4
91.147.107.7:443 href · ×3
185.22.66.192:443 href · ×2
144.31.19.120:443 href · ×2
47.227.150.1:5000 href · ×1
217.92.4.76:8888 href · ×1
103.136.150.116:443 href · ×1
217.226.188.143:80 href · ×1
192.238.201.27:443 href · ×1
185.227.144.120:443 href · ×1
103.136.150.229:443 href · ×1
104.233.169.28:443 href · ×1
107.149.224.46:80 href · ×1
74.208.31.208:443 href · ×1
24.67.40.193:8080 href · ×1
103.136.150.19:443 href · ×1
190.188.1.206:80 href · ×1
104.233.169.26:443 href · ×1
192.238.201.93:443 href · ×1
103.136.150.43:443 href · ×1
43.128.215.229:80 href · ×1
95.217.221.53:443 href · ×1
107.149.131.97:443 href · ×1
103.136.150.68:443 href · ×1
103.136.150.135:443 href · ×1
132.243.114.134:443 href · ×1
20.196.197.169:443 href · ×1
198.167.242.77:443 href · ×1
62.60.159.129:8081 href · ×1
103.136.150.45:443 href · ×1
212.192.12.62:443 href · ×1
149.154.70.108:443 href · ×1
73.64.0.102:80 href · ×1
31.57.44.28:443 href · ×1
153.80.184.177:443 href · ×1
103.136.150.77:443 href · ×1
176.98.191.24:443 href · ×1
86.12.240.174:443 href · ×1
94.250.249.73:443 href · ×1
79.115.80.37:80 href · ×1
192.119.105.164:443 href · ×1
86.140.245.22:80 href · ×1
103.136.150.100:443 href · ×1
74.48.48.148:443 href · ×1
107.149.219.17:443 href · ×1
95.217.217.39:80 href · ×1
103.136.150.71:443 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
AAAA 2001:67c:4e8:f004::9 2026-05-26 02:46:31.734 2026-07-28 18:09:13.258
A 149.154.167.99 2026-05-26 02:46:31.734 2026-07-28 18:09:13.258