Hostname
telegram.com
Last fetched
telegram.com resolves to 7 IPv4 addresses operated by MACST-SV4 - MacStadium, Inc. in DE. WHOIS lists iana:3786 as the registrar.
Nutrition Label
Resolution chain
telegram.com resolves to 7 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 146.75.118.62 | 146.75.116.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | DE |
| 146.75.38.62 | 146.75.36.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | US |
| 151.101.190.62 | 151.101.188.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | NL |
| 151.101.62.62 | 151.101.60.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | GB |
| 199.232.46.62 | 199.232.44.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | SG |
| 199.232.58.62 | 199.232.56.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | GB |
| 140.248.134.62 | 140.248.132.0/22 | AS54113 | MACST-SV4 - MacStadium, Inc. | US |
WHOIS identity
- Registrar
- iana:3786
- Organization
- domain administrator
- Contact emails
Subdomains
55 observed subdomains of telegram.com.
Showing 25 of 55. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from telegram.com in the public web crawl.
8,098 sites link to this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for telegram.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | mktomail.com |
| SPF_INCLUDE | spf.gannett.com |
| SPF_INCLUDE | spf.mandrillapp.com |
| SPF_IP | 174.34.50.27 |
Related pages
Pivot deeper into the graph from telegram.com.
- IP · 146.75.118.62
- ASN · AS54113MACST-SV4 - MacStadium, Inc.
- Registrar · iana:3786
- Country · DE
- Email · anonymous-registrant@brandsight.com
- TLD · .com
- Browse hostnames · te…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "telegram.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.