Skip to content

Hostname

name.080.net

Last fetched

name.080.net resolves to 1 IPv4 address operated by AKAMAI-LINODE-AP Akamai Connected Cloud in JP.

Nutrition Label

WHISPER CANON · name.080.netRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/name.080.net

Resolution chain

name.080.net resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
172.234.89.129172.234.80.0/20AS63949AKAMAI-LINODE-AP Akamai Connected CloudJP

WHOIS identity

No WHOIS records are currently associated with name.080.net in WhisperGraph.

Subdomains

1 observed subdomain of name.080.net.

Subdomain
mail.name.080.net

Web-graph footprint

Distinct hostnames that link to or from name.080.net in the public web crawl.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

  • name.080.net

SPF policy

2 SPF mechanisms authorising senders for name.080.net.

MechanismTarget
SPF_MXmail.name.080.net
SPF_MXname.080.net

Related pages

Pivot deeper into the graph from name.080.net.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "name.080.net"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.