Skip to content

Hostname

tellystats.com

Last fetched

tellystats.com resolves to 18.133.207.63, announced in 18.132.0.0/14 by AMAZON-02 - Amazon.com, Inc. in GB. tellystats.com 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 · tellystats.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/tellystats.com

Resolution chain

IPv6 resolution

No AAAA record for tellystats.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of tellystats.com owner
Contact emails
tellystats.com@privatemonster.com, 1eb7d771-cdc2-4ea7-970b-ac908ee78e29@identity-protect.org, 211ce023-49a1-4328-a6bd-fd97380464b3@identity-protect.org, 3ca75940-3961-477a-9c68-d080a5acc2fb@identity-protect.org, 5a07c01a-78cc-4a5c-86c1-5cef9bff09b5@identity-protect.org, c36d888a-25bf-4f7d-95ca-e08330c069de@identity-protect.org, ef7b8916-5f46-4976-8332-e62a93bae495@identity-protect.org, owner-9700404@tellystats.com.whoisprivacyservice.org

Subdomains

Subdomain
files.tellystats.com
www.tellystats.com

Showing 2 of 2 subdomains (2 per page).

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-417.awsdns-52.com
  • ns-618.awsdns-13.net
  • ns-1483.awsdns-57.org
  • ns-1965.awsdns-53.co.uk

MX records

  • mx.zoho.com
  • mx2.zoho.com
  • mx3.zoho.com

SPF policy

  • include: spf.improvmx.com
  • include: zoho.com

Threat-feed evidence

History

Related pages

Pivot from tellystats.com 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: "tellystats.com"})-[: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.