security-server-landing-page--dianneaagroo.replit.app is a Google impersonation page detected by PhishDestroy on 2026-09-07. Risk: critical (100/100). Registrar: Nom-IQ. Status: Last known active. Hosting: Google LLC. VirusTotal: 21/89 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 8 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.
This is an impersonation phishing page hosted as a user app on Replit's public app platform. Its subdomain is built to read like an official security server landing page, a framing aimed at wallet and account holders who expect to act on an urgent security warning. PhishDestroy first flagged it on 2026-09-07. On 2026-10-19 the address was still alive and redirecting visitors elsewhere.
How the scam works
Security-themed phishing pages claim that an account or wallet is at risk, then push the visitor to verify their identity. They do this by having the visitor sign in, enter a recovery phrase or approve an action, and whatever is typed goes straight to the operator. Because the address now redirects, the page a victim actually lands on may differ from the original lure. The page title currently reads "This app isn't live yet", Replit's placeholder text, while our classification is impersonation phishing.
Evidence
On 2026-09-17, 21 of 89 VirusTotal engines flagged the address. Among them were BitDefender, ESET, Emsisoft, Criminal IP, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam group Chong Lua Dao. Google Safe Browsing lists it under social engineering, so Chrome, Firefox and Safari users should see a red warning screen before the page loads. PhishDestroy carries it on its blocklist.
Infrastructure
The 2021-04-16 registration date and the Com Laude registrar belong to replit.app itself, not to the scammer. The operator only needed a free subdomain on a trusted platform, which explains how the lure could be launched quickly and cheaply. Traffic is served from Google LLC infrastructure in the US. The HTTPS certificate from Google Trust Services is issued automatically to every Replit app, so the padlock says nothing about who runs this page.
What to do
If you typed a password or one-time code here, change that password now, end active sessions and reset two-factor authentication on the affected account. If you entered a seed phrase or private key, treat the wallet as compromised and move your funds to a new wallet created on a clean device. If you connected a wallet and signed anything, review and revoke token approvals with a revocation tool. Defenders should block the full hostname, not replit.app as a whole, and report the app to Replit for removal.
Questions about security-server-landing-page--dianneaagroo.replit.app
Is security-server-landing-page--dianneaagroo.replit.app legit?
No. PhishDestroy classifies security-server-landing-page--dianneaagroo.replit.app as a Google impersonation page (risk: critical, 100/100); it was first detected on 2026-09-07. VirusTotal: 21/89 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 8 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Treat the site as unsafe.
Is security-server-landing-page--dianneaagroo.replit.app safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on security-server-landing-page--dianneaagroo.replit.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used security-server-landing-page--dianneaagroo.replit.app?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
For the registrable domain replit.app behind this subdomain, 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
34.117.33.233
Network ASN
AS396982
Organization
Google Cloud
Observed location
Kansas City, US
Server header
ESF
Nameservers 1
ns-cloud-b4.googledomains.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WR3
Valid from
2026-09-02 11:30:15
Valid until
2026-12-01 12:25:50
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-15 13:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4a74494d584027de8f1b50d93d1683733368fbaea4298191709beefd53e0b0aeCertificate names · 1 SAN
replit.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-23 22:08:18 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 22:08:18 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 · 3 identified
Google Cloud
IaaS
Google Cloud is a suite of cloud computing services.
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 matches8
Same favicon hash or the same page title as this host.
4 evidence signal groups linked0 stored notification recordsLast known active
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including security-server-landing-page--dianneaagroo.replit.app)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
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 phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
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
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
