Skip to content

Hostname

teachingtextbooksapp.com

Last fetched

teachingtextbooksapp.com resolves to 100.51.202.126, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. teachingtextbooksapp.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 · teachingtextbooksapp.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/teachingtextbooksapp.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
0c7ec27c-24f3-4183-9915-b18c47a9eec7@identity-protect.org, 38cb8fc9-82f1-4c34-ad65-d5a7543630f7@identity-protect.org, 57da0ce4-f6bf-4236-9512-e7672adb9fd6@identity-protect.org, 65c0023a-b438-4742-8ef0-6c64f1abc35b@identity-protect.org, dcf55791-d87c-4e66-96a9-ee5c0dae6378@identity-protect.org, f6ecd5b9-609e-4d49-a2fd-817cae972f3a@identity-protect.org, owner-12050383@teachingtextbooksapp.com.whoisprivacyservice.org, owner-3265267@teachingtextbooksapp.com.whoisprivacyservice.org

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

  • ns-409.awsdns-51.com
  • ns-987.awsdns-59.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
  • ns-1461.awsdns-54.org
  • ns-1796.awsdns-32.co.uk

Threat-feed evidence

History

Related pages

Pivot from teachingtextbooksapp.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: "teachingtextbooksapp.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.