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.
4trigger.com was observed on 2026-10-07 with a PageSpeed performance score of 80, and is internally listed by PhishDestroy. The domain was checked by OTX and VirusTotal on the same date, providing multiple sources for assessment.
Recorded Evidence
OTX recorded four pulses for 4trigger.com on 2026-10-07. VirusTotal scanned the domain with 92 scanners on 2026-10-07 and reported zero detections. The domain was registered with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-09-24. Its SSL certificate was issued by Google Trust Services / WE1 and scanned on 2026-10-07.
Interpretation
The evidence for 4trigger.com includes observations from OTX, VirusTotal, and the internal PhishDestroy listing, each offering distinct perspectives. The registration and SSL certificate details provide context for the domain's technical setup. These records allow for comparison of external and internal monitoring sources, and their dated nature supports chronological review.
Recommended Actions
To further evaluate 4trigger.com, retain the OTX pulse records and VirusTotal scan results for ongoing comparison. Preserve the internal PhishDestroy listing and PageSpeed performance score as reference points. Use these dated observations to inform future monitoring and review efforts for the domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Active
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 02:44:01 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-09-24 16:35:18 UTCchecked 2026-10-09 04:29:56 UTC
Observed timelinelast reachable: 2026-10-13 02:44:01 UTClast content: 2026-10-13 02:44:01 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 4trigger.com· checked Oct 7, 2026
80
Needs Work
Performance
FCP
2.56s
First Contentful Paint
LCP
4.62s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.86s
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-07 12:46:46 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.158.133.1.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 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
