Skip to content

Hostname

sauto.cc

Last fetched

sauto.cc resolves to 172.104.44.239, announced in 172.104.32.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in SG. sauto.cc 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 · sauto.ccRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/sauto.cc

Resolution chain

IPv6 resolution

No AAAA record for sauto.cc is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of sauto.cc owner
Contact emails
5b3e4111-08f9-43c2-b1b5-a333515e1e90@identity-protect.org, 5cd7c544-b6f2-4ce6-a2da-3272326a961c@identity-protect.org, 7862c349-aae9-4f8f-9b09-0d5f4e8b5b2c@identity-protect.org, 965da7fe-8084-4d50-a016-faf61e6691be@identity-protect.org, 98e6765a-4a40-49fb-92fa-72afd8e52d35@identity-protect.org, c65f2182-204e-463b-92a7-ff98c6335892@identity-protect.org, c75bd49f-f77a-4028-8ad3-1b760331827c@identity-protect.org

Subdomains

Subdomain
www.sauto.cc

Showing 1 of 1 subdomain (1 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-437.awsdns-54.com
  • ns-616.awsdns-13.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-1143.awsdns-14.org
  • ns-1641.awsdns-13.co.uk

Threat-feed evidence

History

Related pages

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