Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
The domain lyfeorg.com returned an HTTP status of 200 on 2026-10-12, documenting a successful response at that time. Additionally, the domain was listed on two external blocklists, MetaMask and SEAL, as recorded on the same date.
Recorded Evidence
VirusTotal checked lyfeorg.com on 2026-10-11, reporting 6 detections out of 92 scanners. OTX pulses were observed for the domain on 2026-10-12, with a total of 4 recorded pulses. The domain was registered through GoDaddy.com, LLC on 2026-08-29, and its SSL certificate was issued by GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1, with the certificate scan completed on 2026-10-12. PhishDestroy internally listed the domain, and a PageSpeed performance score of 72 was recorded on 2026-10-12.
Interpretation
The VirusTotal record contains a quantitative scan result, measuring detections across multiple scanners for lyfeorg.com. The OTX record documents pulse activity, which is a form of threat intelligence sharing. These sources provide technical measurements and listings that are relevant for reviewing the domain's security context. The timeline of observations, including registration and certificate issuance, offers a snapshot of the domain's infrastructure and its presence in external blocklists.
Recommended Actions
For lyfeorg.com, retain the VirusTotal scan results and OTX pulse records for ongoing comparison. Preserve the HTTP status record and external blocklist entries for future reference. Review the PageSpeed performance score alongside other technical evidence to monitor any changes in the domain's recorded profile.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 lyfeorg.com· checked Oct 12, 2026
72
Needs Work
Performance
FCP
1.86s
First Contentful Paint
LCP
3.75s
Largest Contentful Paint
CLS
0.061
Cumulative Layout Shift
TBT
583ms
Total Blocking Time
SI
2.4s
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-12 09:56:13 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 76.223.105.230.
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.
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.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
4 evidence signal groups linked0 reports recordedLast known active
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · lyfeorg.com
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.
(US)
