Skip to content

Hostname

bs.had.pm

Last fetched

bs.had.pm resolves to 212.8.245.252, announced in 212.8.245.0/24 by ITLDC-EU - ROUTE 95 LLC in NL. bs.had.pm 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 · bs.had.pmRouting diversity1.5/10Peering density5.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/bs.had.pm

Resolution chain

IPv6 resolution

No AAAA record for bs.had.pm is recorded in WhisperGraph.

Attribution

route

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bs.had.pm. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Mail and authentication

Nameservers

  • ns3.zomro.com
  • ns1.zomro.net
  • ns2.zomro.ru
  • ns4.zomro.su

SPF policy

  • mx: bs.had.pm

Threat-feed evidence

History

Related pages

Pivot from bs.had.pm 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: "bs.had.pm"})-[: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.