telegram.de is registered with whois.denic.de. Its SSL certificate from Google Trust Services is valid until 4 Jan 2027, and the site supports HTTP/3.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
1 of 5 protections set up
Lists the servers allowed to send email for this domain.
v=spf1 -allNo key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
0 of 6 recommended headers
The page is served over plain HTTP, so HTTPS can’t be enforced.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
From robots.txt. “Partly blocked”: kept out of some pages, not the homepage. Not every crawler follows it. llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
Is telegram.de’s name taken on other extensions?
Every IP address telegram.de resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| telegram.de | 104.21.85.75 | 300 |
| telegram.de | 172.67.203.133 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| telegram.de | 2606:4700:3034::ac43:cb85 | 300 |
| telegram.de | 2606:4700:3036::6815:554b | 300 |
| Host | Mail server | TTL |
|---|---|---|
| telegram.de | 0 localhost | 300 |
| Host | Name server | TTL |
|---|---|---|
| telegram.de | dean.ns.cloudflare.com | 86400 |
| telegram.de | zariyah.ns.cloudflare.com | 86400 |
| Host | Text | TTL |
|---|---|---|
| telegram.de | "v=spf1 -all" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| telegram.de | dean.ns.cloudflare.com dns.cloudflare.com 2416814059 10000 2400 604800 1800 | 1800 |
Other domains served from 188.114.96.1. Normal for shared hosting and CDNs.
No reviews yet. Used telegram.de? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
telegram.de has no community safety rating yet. Its SSL certificate is valid until 4 Jan 2027. See Security →
telegram.de is registered through whois.denic.de. See WHOIS →
telegram.de is served from 4 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for telegram.de. May be redacted by privacy services.
Domain: telegram.de Status: connect
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with telegram.de. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, http://telegram.de/
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 26 Oct 2026.