Skip to content

Hostname

asp.be

Last fetched

asp.be resolves to 80.65.128.81, announced in 80.65.128.0/20 by ASP-BE-AS - ASP SA in BE. asp.be 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 · asp.beRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/asp.be

Resolution chain

IPv6 resolution

No AAAA record for asp.be is recorded in WhisperGraph.

Attribution

asp

ORIGIN_AS

WHOIS identity

Registrar
registrar:asp.be

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns3.asp.be
  • ns4.asp.be
  • ns5.asp.be

MX records

  • asp-be.mail.protection.outlook.com

SPF policy

  • include: 2j4oy9ah4.spf.checkpoint-spf.com
  • include: spf.protection.outlook.com
  • include: spf.flowmailer.net

Threat-feed evidence

History

Related pages

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