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.
The domain revenuehttps.com was documented with a ScamSniffer blocklist entry on 2026-10-13, providing a dated reference for its inclusion in external security listings. A PageSpeed performance score was also measured, offering insight into its technical profile.
Recorded Evidence
VirusTotal checked revenuehttps.com on 2026-10-10, recording 0 detections out of 92 total scanners. OTX documented 4 pulses for the domain as of 2026-10-13. ScamSniffer listed revenuehttps.com on its blocklist on 2026-10-13. PhishDestroy internally listed the domain on 2026-10-13, and a PageSpeed performance score of 70 was recorded on the same date. The domain was registered with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-10-05.
Interpretation
PhishDestroy contains an internal listing for revenuehttps.com, which documents its inclusion in a security-focused database. VirusTotal provides a technical measurement by recording the number of detections from multiple scanners. The presence of a ScamSniffer blocklist entry and OTX pulses adds context to the domain's profile across external intelligence sources. The recorded dates allow for comparison of the domain's timeline and its review by different security sources.
Recommended Actions
For revenuehttps.com, preserve the ScamSniffer blocklist entry and the internal listing from PhishDestroy for ongoing reference. Compare VirusTotal's scanner results with future scans to monitor any changes in detection status. Retain OTX and PageSpeed records to support further technical and security analysis.
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-13 06:14:49 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 06:14:49 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.
Google PageSpeed Insights — mobile performance audit of revenuehttps.com· checked Oct 13, 2026
70
Needs Work
Performance
FCP
4.84s
First Contentful Paint
LCP
4.89s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.84s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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 06:14:49 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
黑名单检测
见于 1 blocklist: ScamSniffer
2026年10月13日
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Sei
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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
