PhishDestroy identifies lovofx.com as a live credential-phishing domain mimicking a foreign-exchange broker to harvest user login and payment data. The site was registered on November 11, 2018 via GoDaddy, resolves to 173.236.254.52, and currently shows zero detections out of 95 VirusTotal engines. Although the SSL certificate is issued by Let’s Encrypt, the domain’s age and low detection rate suggest it is actively used in low-volume spear-phishing targeting finance professionals. Analysts correlated lovofx.com with a spike in fake “platform login” emails sent to traders; the domain was only flagged internally after an anomalous spike in failed login attempts against corporate webmail. Historical pivoting reveals the registrar GoDaddy lists the registrant country as Russia, and passive DNS shows a single A record pointing to the same IP since registration. VirusTotal reports 0/95 detections (SHA-256 8c7b42e0…), and the domain is absent from Spamhaus, OpenPhish, and PhishTank blocklists as of today—indicating a recently activated or highly targeted campaign. If you visited lovofx.com, immediately rotate passwords used on the site, enable MFA everywhere, and scan endpoints for follow-on malware. Report the domain to your security team via ticket number 94c4ae and block the IP 173.236.254.52 at the firewall. Treat any credentials entered on the site as compromised and initiate an incident response workflow.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-185612.invalid', port=80): Max retries exceeded with url: / (Caused by
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedMar 28, 2026
Submitted URLhttps://www.lovofx.com/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
173.236.254.52
Network ASN
AS26347
Organization
DreamHost
Observed location
Ashburn, US
Server header
Apache
Nameservers 1
ns3.dreamhost.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-03-15 14:37:29
Valid until
2026-06-13 14:37:28
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-29 06:36:39 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd9bd544fe9d6cedfbf72fb06b9ebee98df8630110dabc2c2bf1d92ac0a9a291aCertificate names · 1 SANs
lovofx.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:31:00 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:13:58 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.
Technologies · 8 identified
W
WordPress
CMS
Open-source CMS powering over 40% of websites worldwide.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-185612.invalid· checked Mar 28, 2026
68
Needs Work
Performance
FCP
4.12s
First Contentful Paint
LCP
4.53s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
133ms
Total Blocking Time
SI
6.99s
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.
Domain Status Transition2026-09-25 01:31:11 UTC
Domain state transitioned from alive to dead.
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.
Threat Ingested
duplicate-disabled-185612.invalid detected and queued for full analysis
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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
614 hours elapsed from detection to the first unavailable 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 recordedContent unavailable
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 →
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.
Content matches1
Same favicon hash or the same page title as this host.
Report 
(US)
