Is btcblack.it legit? TrustSniffer's high-trust assessment: 100/100

Overview

The website operates as a public cybersecurity clearinghouse, providing DNS-queryable blocklists for identifying Bitcoin wallets associated with illicit activity, abusive email accounts, and spam-content patterns for integration into security systems and email filters.

Scam/Impersonation Risk

No identity contradictions, phishing indicators, brand impersonation, or malicious reputation findings were observed. Its narrowly defined technical purpose is consistent across the available content and historical record: the Bitcoin list addresses wallet-abuse intelligence, while separate lists cover abusive email-service accounts, individual freemail accounts, and fuzzy hashes of related spam variants. This coherent service model, established provenance, and clean external reputation support the conclusion that the site is legitimate rather than a deceptive cryptocurrency operation.

• The domain was registered in 2018 and is approximately 7.65 years old; the registration is maintained through OVH.
• The archive record contains 81 snapshots spanning May 2019–May 2026, representing eight years of tracked history without an established suspicious repurposing or semantic shift.
• Reputation checks recorded zero malicious and zero suspicious detections, no external threat-list hit, and no reported abuse against the assessed infrastructure.
• The homepage describes standard DNS lookup integration and contains no login form, hidden form, financial solicitation, wallet connection, or sensitive-data request.

Regulatory Verification Notes

The service presents itself as an informational threat-intelligence utility supported by sponsorship, not as a broker, exchange, custodian, investment product, or transaction platform. Accordingly, the absence of an asserted financial-services licence is consistent with the stated business model and is not evidence of regulatory misconduct. The available homepage identifies SNB as sponsor and provides an abuse-reporting channel, although the supplied page set does not establish a detailed legal-entity statement or formal service terms; this is a limited documentation consideration rather than a legitimacy concern.

• The homepage identifies the service as “BTC Black — Blocklist Threat Clearinghouse” and names SNB as its sponsor.
• The homepage presents no deposit mechanism, consumer sale, trading facility, investment return, or licensing claim.
• The hosting infrastructure is served from AS16276 (OVH - OVH SAS, FR).
• The site’s transport encryption uses a YR1-issued domain-validated TLS certificate, valid until 2026-09-20.

What to Verify Next

Enterprise adopters should validate the DNS response formats, list-update behavior, false-positive handling, and operational availability in a controlled environment before incorporating the feeds into production filtering. Procurement or compliance teams may also request the service operator’s usage terms, data-sourcing methodology, correction process, retention practices, and service-level commitments, while independently confirming official contact channels for any formal relationship.

• The homepage states that each blocklist can be queried independently through standard DNS and integrated into existing security systems and email filters.
• The Bitcoin list is described as covering wallet addresses associated with fraud, scams, ransomware, and other illicit activity.
• The email-focused lists use hashed account identifiers, while the content-focused list uses ZOrder locality-sensitive hashes.
• The site publishes a channel for enquiries and abuse reports but exposes no interactive submission form.

Summary Verdict

The website is a legitimate, established, and trustworthy cybersecurity utility. Its coherent identity, sustained provenance, benign observed behavior, and clean reputation collectively support a high-confidence trust posture with no contradictory risk signals.

Infrastructure Integrity

The site uses OVH-hosted protective CDN/WAF infrastructure in France; the single observed address was an edge endpoint, and the origin server was not exposed during the assessment. This arrangement reduces direct origin exposure and is a mitigating security control, although infrastructure protection alone is not proof of legitimacy.

Closing Assessment

Normal interaction, including routine access, standard use, and account login if such functionality is introduced through the official service, is appropriate; production reliance should follow ordinary technical validation and supplier due diligence.