How is telegram.org?

Looks fine risk 0/100

Registered 23 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 301 ms.

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.

Site

200

301 ms

HTTPS

136 d

left on a GoDaddy.com certificate

Age

23 years

registered 2003-12-15

Blocklists

listings across 5 lists

Everything we looked at

DNS records5 record types

A	149.154.167.99
AAAA	2001:67c:4e8:f004::9
MX	10 mx101.telegram.org 15 mx110.telegram.org
NS	ns-cloud-b1.googledomains.com ns-cloud-b2.googledomains.com ns-cloud-b3.googledomains.com ns-cloud-b4.googledomains.com
TXT	google-site-verification=R-3XYX47JUVHva3pnhnyjx5D72PtSnjtLMLj_tymTAc google-site-verification=hAtj8VzR8lGDcv80yGd0ST-pMHU8WNU0lkswaau3v2w v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/30 ip4:149.154.160.0/20 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all yahoo-verification-key=NRNCv6/IcZMkSv28KI97E4zgZVMkk4PejCwNSh8So2k=

RegistrationGoDaddy.com, LLC

registrar	GoDaddy.com, LLC
registered	2003-12-15
expires	2031-12-15
last changed	2026-08-12
nameservers	ns-cloud-b1.googledomains.com ns-cloud-b4.googledomains.com ns-cloud-b2.googledomains.com ns-cloud-b3.googledomains.com
status	client delete prohibited client renew prohibited client transfer prohibited client update prohibited

registered 2003-12-15expires 2031-12-15

HTTPS certificate136 days left

valid	yes
issuer	GoDaddy.com
covers	*.telegram.org, telegram.org
protocol	TLSv1.3

issued 2026-08-25expires 2027-03-11

DNSSECinsecure

Domain is not signed with DNSSEC

. → org → telegram.org

Email authenticationexcellent

SPF	pass `v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/30 ip4:149.154.160.0/20 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all`
DMARC	pass policy reject
DKIM	found: mail

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade B · 160/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

30/45missing: CAA Records, DKIM Presence

Advanced Security

25/25

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop149.154.167.99Barracuda149.154.167.99UCEPROTECT Level 1149.154.167.99

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.

curl "https://how.is/v1/domain/trust?domain=telegram.org" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=telegram.org"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on telegram.org. Reference: /llms.txt.

Watch telegram.org. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.

Watch — $1 / 30 days