Skip to content

Hostname

blackdiamondring.org

Last fetched

blackdiamondring.org resolves to 89.163.139.90, announced in 89.163.128.0/17 by MYLOC-AS - WIIT AG in DE. blackdiamondring.org 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 · blackdiamondring.orgRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/blackdiamondring.org

Resolution chain

Attribution

wiit

ORIGIN_AS

WHOIS identity

Registrar
iana:3862
Registrant organisation
domain administrator
Contact emails
pw-63fd94617c3bb04de1cc00c7a4662d1c@privacyguardian.org, pw-6e648d7f76fb62d686dc93bd1901621b@privacyguardian.org, pw-f65fecb12a4588ff1c2a8cf393a850ef@privacyguardian.org

Subdomains

Subdomain
mail.blackdiamondring.org
www.blackdiamondring.org

Showing 2 of 2 subdomains (2 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
  • ns1ml136.pub-dns.org
  • ns1nd23.pub-dns.org
  • ns2ml136.pub-dns.org
  • ns2nd23.pub-dns.org

MX records

  • mail.blackdiamondring.org

SPF policy

  • a: blackdiamondring.org
  • mx: blackdiamondring.org
  • ip: 89.163.241.64

Threat-feed evidence

History

Related pages

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