Skip to content

Hostname

metro.net

Last fetched

metro.net resolves to 14 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:2 as the registrar.

Nutrition Label

WHISPER CANON · metro.netRouting diversity5.2/10Peering density9.5/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/metro.net

Resolution chain

metro.net resolves to 14 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
13.56.73.22613.56.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
13.56.75.3713.56.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
13.57.70.1513.57.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
13.57.84.2013.57.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
52.52.129.10252.52.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.US
52.52.215.24052.52.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.US
52.53.39.7252.52.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.US
54.153.23.7854.153.0.0/17AS16509AMAZON-02 - Amazon.com, Inc.US
54.183.123.854.183.0.0/17AS16509AMAZON-02 - Amazon.com, Inc.US
54.193.213.11754.193.128.0/17AS16509AMAZON-02 - Amazon.com, Inc.US
54.215.202.9054.215.192.0/18AS16509AMAZON-02 - Amazon.com, Inc.US
54.241.153.1654.241.128.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
54.241.212.2554.241.192.0/18AS16509AMAZON-02 - Amazon.com, Inc.US
54.176.142.17254.176.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

Registrar
iana:2
Organization
los angeles county metropolitan transportation authority
Contact emails

Subdomains

168 observed subdomains of metro.net.

Web-graph footprint

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

3,146 sites link to this hostname.

Threat posture

History

Mail and authentication

SPF policy

3 SPF mechanisms authorising senders for metro.net.

MechanismTarget
SPF_INCLUDEspf1.metro.net
SPF_INCLUDEspf2.metro.net
SPF_INCLUDEspf3.metro.net

Related pages

Pivot deeper into the graph from metro.net.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "metro.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.