Skip to content

Hostname

papperas.be

Last fetched

papperas.be is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. papperas.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 · papperas.beRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/papperas.be

Resolution chain

No IPv4 resolution is recorded for papperas.be in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
registrar:nomeo

Subdomains

Subdomain
help.papperas.be
nl.papperas.be
www.papperas.be

Showing 3 of 3 subdomains (3 per page).

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns14.wixdns.net
  • ns15.wixdns.net

MX records

  • papperas.be.clean.connectify.be
  • papperas.be.clean-backup.connectify.be

SPF policy

  • ip: 81.95.117.132/32
  • ip: 81.95.117.138/32
  • ip: 82.143.92.18/32
  • ip: 84.199.87.192/28
  • ip: 81.83.4.225/32
  • ip: 213.224.20.34/32
  • ip: 213.224.39.41/32
  • include: spf.mail.nomeo.be
  • a: papperas.be
  • mx: papperas.be
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • ip: 84.199.87.194

Threat-feed evidence

History

Related pages

Pivot from papperas.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: "papperas.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.