Skip to content

Hostname

telesystem.us

Last fetched

telesystem.us resolves to 199.60.103.226, announced in 199.60.103.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. telesystem.us is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · telesystem.usRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/telesystem.us

Resolution chain

IPv6 resolution

No AAAA record for telesystem.us is recorded in WhisperGraph.

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
buckeye telesystem,
Contact emails
chustwayte@sharedsvcs.com, rjwalker@cablesystem.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1.buckeyecom.net
  • ns2.buckeyecom.net
  • ns3.buckeyecom.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • telesystem-us.mail.protection.outlook.com

SPF policy

  • ip: 192.254.121.248/32
  • ip: 72.240.36.32/27
  • ip: 52.203.41.93/32
  • include: _spf.coredial.com
  • include: spf.protection.outlook.com
  • include: spf.us.exclaimer.net
  • mx: telesystem.us
  • ip: 208.84.248.11
  • ip: 208.84.251.130
  • ip: 72.240.1.246

Threat-feed evidence

History

Related pages

Pivot from telesystem.us into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "telesystem.us"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.