Skip to security report
Domain security and threat intelligence
inkonchain.top favicon

inkonchain.top

Registrar
NiceNIC
Resolved IP
188.114.97.3
Threat verdict High
Availability Unverified No conclusive current response is stored Observed
Source: HTTP probe
Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Scam type: Impersonation
OTX: 3 refs Aug 31, 2026 CDN
API
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Spamhaus DBL
DBL_PHISH
OTX references
URLScan
URLScan
TLS Certificate
Expired or unverified
PhishDestroy
DestroyList
Listed

Source evidence

6 sources

Spamhaus DBL

DBL_PHISH

VirusTotal

checked — no detections recorded

Report

OTX

3 community references

Report

URLScan capture

stored report

Report

URLScan verdict

Analysis completed

Report

Google Safe Browsing

Checked; no threat flag recorded

Report
Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Evidence Summary

High
OTX
3 community refs
URLScan
Stored capture

Assessment

On 2026-10-01, inkonchain.top returned an HTTP 502 status, indicating a server-side error. The domain was also listed on the MetaMask and SEAL external blocklists as of the same date.

Recorded Evidence

On 2026-10-01, a check recorded HTTP status 502 for inkonchain.top. The domain was listed on MetaMask and SEAL blocklists on 2026-10-01. VirusTotal, checked on 2026-09-10, reported 0 detections out of 89 scanners. OTX, also checked on 2026-09-10, recorded 3 pulses. The registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED.

Interpretation

The HTTP 502 status and blocklist listings are distinct observations reflecting server issues and potential security concerns. VirusTotal and OTX provide additional perspectives from separate sources, each with its own scope and assessment methods. The recorded dates allow for comparison of results across various security platforms.

Recommended Actions

For inkonchain.top, retain the HTTP status record, blocklist entries, VirusTotal scanner results, and OTX pulse count as separate evidence for future reference. Compare these records in subsequent reviews to monitor for changes or new observations across the different sources.

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='inkonchain.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 1 capture

TLS Certificate
Hostname coverage not recorded · Issued by WE1

Domain details

Domain
URLScan Verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX Tags 2026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Elapsed Since First Report 11 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Unverified.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • cloe.ns.cloudflare.com.

Location describes the IP network.

TLS certificate

Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-13 20:21:07 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-14 10:50:29 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-08-31 08:28:23 UTC current episode first observed: 2026-09-11 18:17:21 UTC observed RIP window: 2026-08-31 08:28:23 UTC → 2026-09-11 18:17:21 UTC · 273.82h midpoint estimate ≈ 2026-09-06 01:22:52 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-10 22:00:26 UTC
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-09-10 20:31:37 UTC
    Domain ingestion complete. Initial state is marked as alive.

Threat Response Pipeline

Discovery
Analysis
Monitoring

9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
inkonchain.top detected and queued for full analysis
Aug 31, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 11, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 14, 2026
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 11, 2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 11, 2026
DestroyList Published
Aug 31, 2026
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Public Blocklist Status

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

3 evidence signal groups linked 0 reports recorded Unverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Europol
Find the official reporting channel for your EU country
National police directory
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/inkonchain.top"
  title="PhishDestroy threat report for inkonchain.top"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>