Skip to content

Hostname

https-latency-map.sginfra.net

Last fetched

https-latency-map.sginfra.net resolves to 13.159.228.235, announced in 13.158.0.0/15 by AMAZON-02 - Amazon.com, Inc. in JP. https-latency-map.sginfra.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 · https-latency-map.sginfra.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.7/10canon.whisper.security/host/https-latency-map.sginfra.net

Resolution chain

IPv6 resolution

No AAAA record for https-latency-map.sginfra.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for https-latency-map.sginfra.net. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

  • ns-54.awsdns-06.com
  • ns-127.awsdns-15.com
  • ns-138.awsdns-17.com
  • ns-210.awsdns-26.com
  • ns-232.awsdns-29.com
  • ns-417.awsdns-52.com
  • ns-467.awsdns-58.com
  • ns-598.awsdns-10.net
  • ns-613.awsdns-12.net
  • ns-699.awsdns-23.net
  • ns-785.awsdns-34.net
  • ns-827.awsdns-39.net
  • ns-953.awsdns-55.net
  • ns-982.awsdns-58.net
  • ns-1036.awsdns-01.org
  • ns-1076.awsdns-06.org
  • ns-1125.awsdns-12.org
  • ns-1312.awsdns-36.org
  • ns-1325.awsdns-37.org
  • ns-1326.awsdns-37.org
  • ns-1511.awsdns-60.org
  • ns-1566.awsdns-03.co.uk
  • ns-1683.awsdns-18.co.uk
  • ns-1689.awsdns-19.co.uk
  • ns-1722.awsdns-23.co.uk
  • ns-1850.awsdns-39.co.uk
  • ns-1973.awsdns-54.co.uk
  • ns-2017.awsdns-60.co.uk

Threat-feed evidence

History

Related pages

Pivot from https-latency-map.sginfra.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: "https-latency-map.sginfra.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.