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.
fvjdfvbdfjbvhjdbsjhdv.com returned an HTTP status code 200 on 2026-10-11, as recorded in the HTTP status source. On the same date, ScamSniffer included the domain on its external blocklist, providing an additional reference point for review.
Recorded Evidence
ScamSniffer listed fvjdfvbdfjbvhjdbsjhdv.com on its blocklist as of 2026-10-11. The domain was first observed on 2026-10-11 and registered through NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-10-01. OTX documented one pulse referencing this domain on 2026-10-11. PhishDestroy also recorded an internal listing for the domain, and its SSL certificate was issued by Let's Encrypt / YE2, scanned on 2026-10-11.
Interpretation
The HTTP status source contains a technical measurement of the domain's response on a specific date. ScamSniffer and OTX each provide dated records documenting how fvjdfvbdfjbvhjdbsjhdv.com was referenced in their respective intelligence sources. These observations cover both technical and blocklist contexts, supporting a broader review of the domain's recorded footprint.
Recommended Actions
Preserve the ScamSniffer blocklist entry and OTX pulse records for fvjdfvbdfjbvhjdbsjhdv.com for future reference. Compare these with additional HTTP status results and internal listings from PhishDestroy to track any notable changes in the domain's recorded evidence.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 09:54:10 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 09:54:10 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.
Threat First Observed2026-10-11 09:54:10 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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
