Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, solana-memecoins-interface.netlify.app returned HTTP status 404 in an HTTP check. The domain was first observed on 2026-09-14 and appears on two external blocklists, MetaMask and SEAL.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404 for solana-memecoins-interface.netlify.app. The domain was first observed on 2026-09-14. External blocklist checks on 2026-10-01 listed the domain on MetaMask and SEAL. VirusTotal on 2026-09-22 recorded 4 detections across 89 scanners. The domain resolved to IP address 35.157.26.135, associated with AWS EC2 (eu-central-1) in DE. PhishDestroy's internal listing was recorded as true.
Interpretation
The MetaMask and SEAL listings and the PhishDestroy internal listing are separate source records that each flag the domain, while the VirusTotal result reflects its own scanner set on its own date. The 2026-10-01 HTTP 404 describes only the response recorded that day, not all content that may exist on the domain. Because the first observation, VirusTotal check, and HTTP check fall on different dates, they should be read as separate dated measurements rather than a single timeline.
Recommended Actions
Preserve the MetaMask and SEAL blocklist records for solana-memecoins-interface.netlify.app, and keep the PhishDestroy internal listing as a separate record. Compare the VirusTotal result with the external blocklist entries in separate reviews, since each source uses its own criteria. Retain the HTTP check record alongside the first-observed entry so future reviews can compare dated observations of solana-memecoins-interface.netlify.app.
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.
IP ContextNetlify shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerNetlify(US)
HTTP Status404 Not Found
Time to First Unavailability6 days
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 DetectedSep 14, 2026
Page Title
Solana Token — $TOKEN Airdrop
Impersonates
Solana
TLS Certificate
Hostname coverage not recorded·
Issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
35.157.26.135
Network ASN
AS16509
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt, DE
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Hostname coverage
Hostname coverage not recorded
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.
Primary outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-11 01:29:59 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-14 14:28:09 UTCcurrent episode first observed: 2026-10-01 01:53:33 UTCobserved RIP window: 2026-09-14 14:28:09 UTC → 2026-10-01 01:53:33 UTC · 395.42hmidpoint estimate ≈ 2026-09-22 20:10:51 UTC · precision low · basis bounded
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 · 2 identified
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
Last analyzed First positive detection Previous stored snapshot: 4 detections
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
VIPRE
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.
VirusTotal Detections Update2026-09-21 11:10:47 UTC
VirusTotal scanner detections updated from 1 to 4. Added scanner alerts: ChainPatrol, Forcepoint ThreatSeeker, alphaMountain.ai.
Domain Status Transition2026-09-20 22:00:20 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-20 20:03:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
solana-memecoins-interface.netlify.app 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 21, 2026
Time to First Unavailability
152 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 a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. 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 matches3
Same favicon hash or the same page title as this host.
Chainabuse — flag scam wallets across exchanges & platforms
Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do crypto scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
Bookmark official sites — never click links from emails, DMs, or ads
Read every approval — verify permissions before signing. Reject unlimited approvals
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
HTML · IFRAME
Embed This Report
Share this threat intelligence on your website or blog
READ-ONLY
embed.html
<iframesrc="https://phishdestroy.io/embed/domain/solana-memecoins-interface.netlify.app"title="PhishDestroy threat report for solana-memecoins-interface.netlify.app"width="100%"height="320"loading="lazy"referrerpolicy="no-referrer"sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"style="border:0;border-radius:12px;max-width:100%"></iframe>
(US)
