Skip to content

Hostname

gtsstatic.net

Last fetched

gtsstatic.net resolves to 75.2.111.92, announced in 75.2.96.0/20 by AMAZON-02 - Amazon.com, Inc. in US. gtsstatic.net 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 · gtsstatic.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/gtsstatic.net

Resolution chain

IPv6 resolution

No AAAA record for gtsstatic.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
identity protection service
Contact emails
5ecc89ab-987e-47e6-818b-efe69af713c1@identity-protect.org, 7373c2f9-b42e-4eb0-8ffa-23043be3e0fa@identity-protect.org, 7f927b91-1d28-4066-9c43-da2649dc49bc@identity-protect.org, a6ec14cb-0bf5-46d8-a880-a63ef7ca0802@identity-protect.org, bd85da5f-334d-4e18-bb7d-f155599d65d1@identity-protect.org, f08d26e9-6b5a-40ac-8411-77829eca73c8@identity-protect.org, owner-1756195@gtsstatic.net.whoisprivacyservice.org, owner-5428400@gtsstatic.net.whoisprivacyservice.org, owner-6288170@gtsstatic.net.whoisprivacyservice.org, owner-8981171@gtsstatic.net.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-132.awsdns-16.com
  • ns-595.awsdns-10.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-1039.awsdns-01.org
  • ns-1719.awsdns-22.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

SPF policy

  • include: amazonses.com

Threat-feed evidence

History

Related pages

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