thetelegram.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

39risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

1Medium

4Low

2Info

Collected 3 hours ago26.7sfrom cache

Certificate Transparency8
DNS resolution11
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs13
Registration
DNS posture4
Email authentication1
Certificate
Security headers6
Archived URLs
Analysis8

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.thetelegram.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@thetelegram.com"`, review the reports, then move to p=quarantine and p=reject.
asset: thetelegram.com
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 35.212.247.87:22
35.212.247.87 (related.thetelegram.com) reports openssh 10.2p1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 35.212.247.87
dev.thetelegram.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.thetelegram.com
staging.thetelegram.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: staging.thetelegram.com
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: thetelegram.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: thetelegram.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: thetelegram.com

final https://www.saltwire.com/category/newfoundland-labrador/status 200time 738msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✓Content-Security-Policy
default-src * 'unsafe-eval' 'unsafe-inline' data: blob:
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
autoplay=(*), camera=(*), display-capture=(*), encrypted-media=(*), fullscreen=(*), geolocation=(*), microphone=(*), pay
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
thetelegram-com.mail.protection.outlook.com
!SPFends in ~all
v=spf1 ip4:24.222.6.230 ip4:52.6.112.187 include:navigacloud.com include:spf.protection.outlook.com include:spf.mtasv.net mx a ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-cloud-c1.googledomains.com ns-cloud-c2.googledomains.com ns-cloud-c3.googledomains.com ns-cloud-c4.googledomains.com

✓Registered with Webnames.ca Inc.28.3 years old
thetelegram.com
✓Registration expiry246 days
2027-05-12
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-cloud-c1.googledomains.com ns-cloud-c2.googledomains.com ns-cloud-c3.googledomains.com ns-cloud-c4.googledomains.com

Address	Ports	Edge	Network
34.111.67.160 thetelegram.com +5	80443	direct	—
70.35.200.17 working.thetelegram.com +3	80443	direct	—
174.129.216.79 shopping.thetelegram.com +2	80443	direct	—
32.187.58.191 classifieds.thetelegram.com +2	80443	direct	—
44.234.228.51 classifieds.thetelegram.com +4	80443	direct	—
35.212.247.87 related.thetelegram.com +1	22	direct	—
44.197.88.97 shopping.thetelegram.com +1	443	direct	—
32.185.85.222 classifieds.thetelegram.com +7	443	direct	—
209.172.61.44 staging.thetelegram.com +1	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

thetelegram.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames