Skip to content

Hostname

would.be

Last fetched

would.be resolves to 2 IPv4 addresses operated by LEASEWEB-NL-AMS-01 Netherlands in NL.

Nutrition Label

WHISPER CANON · would.beRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/would.be

Resolution chain

would.be resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
37.48.72.21337.48.64.0/18AS60781LEASEWEB-NL-AMS-01 NetherlandsNL
37.48.77.8337.48.64.0/18AS60781LEASEWEB-NL-AMS-01 NetherlandsNL

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

Distinct hostnames that link to or from would.be in the public web crawl.

Sample inbound links

Threat posture

History

Related pages

Pivot deeper into the graph from would.be.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "would.be"})-[: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.