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.
bs2bestblacksprut.com was observed returning an HTTP 200 status during a check on 2026-10-01, indicating a successful response at that time. The domain is also listed in the PhishDestroy internal catalogue.
Recorded Evidence
A VirusTotal scan on 2026-09-30 found 4 detections out of 91 scanners for bs2bestblacksprut.com. OTX recorded 3 pulses for the domain on 2026-09-28. An HTTP check on 2026-10-01 returned status 200. The domain was registered on 2026-09-08 with NICENIC INTERNATIONAL GROUP CO., LIMITED. The SSL certificate was issued by Let's Encrypt / YR1 as of a scan on 2026-09-26.
Interpretation
The records from VirusTotal, OTX, and the HTTP check each provide a separate view of bs2bestblacksprut.com at different times. Each source uses its own criteria and methods, so their findings should be considered individually. The presence of the domain in the PhishDestroy internal listing adds further context for review.
Recommended Actions
For future reference, retain the HTTP status record and the VirusTotal scan for bs2bestblacksprut.com as distinct sources. Compare the OTX pulse record and the PhishDestroy internal listing separately to track any changes. Keep the registration and SSL certificate records available for any subsequent domain assessments.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Active
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-12 10:58:02 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-09-08 22:16:55 UTCchecked 2026-09-26 04:26:43 UTC
Observed timelinelast reachable: 2026-10-12 10:58:02 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.
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.
VirusTotal Detections Update2026-09-27 01:19:51 UTC
VirusTotal scanner detections updated from 3 to 2. Added scanner alerts: Forcepoint ThreatSeeker. Resolved alerts: CRDF, SOCRadar.
VirusTotal Detections Update2026-09-26 02:31:59 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-25 19:14:00 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-25 05:08:40 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 111.90.148.120.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(RU)
PhishDestroy Investigation
