Skip to content

Hostname

bitcoin.melroy.org

Last fetched

bitcoin.melroy.org resolves to 77.61.56.117, announced in 77.60.0.0/14 by KPN - KPN B.V. in NL. bitcoin.melroy.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 · bitcoin.melroy.orgRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/bitcoin.melroy.org

Resolution chain

IPv6 resolution

No AAAA record for bitcoin.melroy.org is recorded in WhisperGraph.

Attribution

kpn

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bitcoin.melroy.org. 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

Subdomain
developer.bitcoin.melroy.org

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • ns02.forward.antagonist.net
  • ns01.forward.antagonist.nl

MX records

  • mx1-forward-antagonist-nl.pub.mailpod13-cph3.one.com
  • mx2-forward-antagonist-nl.pub.mailpod13-cph3.one.com
  • mx3-forward-antagonist-nl.pub.mailpod13-cph3.one.com
  • mx4-forward-antagonist-nl.pub.mailpod13-cph3.one.com

SPF policy

  • ip: 141.138.168.0/21
  • ip: 195.211.72.0/22
  • ip: 2a03:3c00:a001::/48
  • ip: 2a03:3c00:a002::/48
  • include: _spf.google.com
  • include: _custspf.g1i.one
  • a: bitcoin.melroy.org
  • mx: bitcoin.melroy.org

Threat-feed evidence

History

Related pages

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