Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Analysis as of July 29 2026 indicates that the domain rewards-fomo.family was registered on June 12 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and currently resolves to the IP address 104.21.30.163. The domain appears on three public security blocklists and is actively blocked by the PhishDestroy, MetaMask, and SEAL filtering services, suggesting that multiple downstream security products have already identified it as malicious. VirusTotal scans show that five of ninety‑one antivirus or URL‑analysis engines have flagged the domain, reinforcing the suspicion of malicious activity despite the limited detection count.
The threat is classified as generic phishing, and the elevated risk rating reflects the combination of recent registration, active blocklist presence, and partial vendor detections. No public information is available regarding SSL certificate details, HTTP response codes, page title, or the exact phishing payload, leaving the precise luring technique uncertain.
Defenders should prioritize blocking or sinkholing the domain at the network perimeter, update proxy and DNS filtering policies to include the three known blocklists, and ensure endpoint security solutions incorporate the latest threat intelligence feeds that reference rewards-fomo.family. Continuous monitoring of the associated IP address for anomalous traffic and periodic re‑scanning with multi‑vendor services are recommended to capture any evolution in the payload or additional detections.
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.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rewards-fomo.family', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
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 DetectedJun 13, 2026
DOM Analysisanalyzed Aug 1, 2026score 95/1001 brand signal
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
Shared CDN edge
Resolved IP
104.21.30.163
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection time
2026-08-01 01:02:25 UTC
Collection source
PhishDestroy collector
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-13 01:28:29 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:18:08 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.
Last analyzed Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
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-08-06 22:15:04 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-08-05 22:38:01 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-07-29 03:12:53 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.30.163.
Threat Response Pipeline
Discovery
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
rewards-fomo.family 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.
Aug 6, 2026
Time to First Unavailability
1293 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 →
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 · rewards-fomo.family
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)
