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.
PhishDestroy first observed io-search-a-opensea-btc-rvn-chrome-ob-utf-8.com on Oct 13, 2026. The hostname explicitly references OpenSea; stored content metadata identifies the same apparent target. Stored page analysis classifies the content as nft scam. Current evidence score: 66/100 (high).
Positive findings are stored from 2 sources: MetaMask and SEAL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 13, 2026 at 10:20 UTC. Additional recorded evidence: On Oct 13, 2026 at 10:20 UTC, VirusTotal recorded 0 detections among 92 engines; AlienVault OTX listed 4 community pulse references (not vendor detections). URLScan captured the page on Oct 13, 2026 at 09:19 UTC.
The collector marked the hostname reachable on Oct 13, 2026 at 09:19 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 13, 2026 at 07:19 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Oct 11, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 172.67.139.163 (AS13335 Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Oct 13, 2026 at 10:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YE2 as the certificate issuer with validity through Jan 9, 2027; checked Oct 13, 2026 at 10:02 UTC.
The content indicators and 2 positive source findings support the current OpenSea-themed nft scam classification.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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
Capture routing
Localarchived 2026-10-13 11:20:33 UTC
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 · 2 captures
Primary capture
1 / 2
URLScan capture
2 / 2
SourcePrimary capture
Recorded2026-10-13 09:19 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttp://io-search-a-opensea-btc-rvn-chrome-ob-utf-8.com/
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 09:19:42 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 09:19:42 UTC
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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
3 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 11:20:33 UTC
Source
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 11:20:33 UTC
Source
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
security.txt
Reachable (legacy)/.well-known/security.txt
HTTP response
200
Observed at
2026-10-13 11:20:33 UTC
Source
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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.
Threat First Observed2026-10-13 09:19:42 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.139.163.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
io-search-a-opensea-btc-rvn-chrome-ob-utf-8.com detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 13, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 13, 2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of OpenSea
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Oct 13, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
3 evidence signal groups linked0 reports recordedUnverified
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.
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 →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(RU)
PhishDestroy Investigation
