PhishDestroy first recorded google-live-maps.com on 2026-10-27. Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-27 07:26 UTC. Retrieved (as stored): 2026-10-27 23:50 UTC. Google Safe Browsing flags it.
Page title: “Shared IP”
More about the sources
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-27 07:26 UTC. Retrieved (as stored): 2026-10-27 23:50 UTC. Use caution — do not enter credentials or personal information.
Risk signals
VirusTotal detections: 17/92Google Safe Browsing: threat flag recorded
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded google-live-maps.com on 2026-10-27. Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-27 07:26 UTC. Retrieved (as stored): 2026-10-27 23:50 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Registrar: Purple IT. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
PhishDestroy listed google-live-maps.com on 2026-10-28 following an intake that cited a Google Safe Browsing social‑engineering warning. The recorded page title is "Shared IP" and the site returned HTTP 200 on the same day. Google Safe Browsing marked the domain as a social‑engineering threat on 2026-10-28. Subsequent scans by VirusTotal, Cloudflare Radar and urlscan.io also reported malicious or phishing indicators.
How the scam works
The detections point to a phishing or social‑engineering risk, a category where attackers mimic trusted services to lure users into revealing credentials or personal data. Such schemes typically present a look‑alike login or request sensitive information, but no specific credential‑harvesting form was observed on the captured page. Because the page only displayed a generic title, the exact malicious payload cannot be confirmed from the available evidence.
Evidence
Google Safe Browsing flagged the domain for social engineering on 2026-10-28. VirusTotal recorded 17 detections out of 92 engines on 2026-10-28, with vendors such as BitDefender, ESET, Fortinet and others labeling it as phishing or malicious. Cloudflare Radar’s scan on 2026-10-28 assigned a phishing verdict and a malicious tag. urlscan.io’s machine‑learning engine gave a score of 74 and marked it malicious on 2026-10-26, while its overall verdict was clean. The external blocklist Phishunt also listed the domain, and PhishDestroy’s internal blocklist includes it as of 2026-10-27. OTX reported zero pulses on 2026-10-28.
Infrastructure
The domain was registered on 2026-02-21 through Purple IT Ltd and is set to expire on 2027-02-21. DNS records resolve to Cloudflare IPs 104.21.89.103 and 172.67.157.223, with AAAA records in Cloudflare’s network. The TLS certificate is issued by Let’s Encrypt (YE2), valid from 2026-10-15 to 2027-01-13, and DNSSEC is not enabled. Nameservers are elly.ns.cloudflare.com and emerson.ns.cloudflare.com.
What to do
Do not enter any Google credentials or personal data on this site; if you have already done so, change passwords and enable two‑factor authentication on the affected accounts. Report the domain to Google Safe Browsing and to your organization’s security team for blocking. Defenders should add google-live-maps.com to web‑filter blocklists, monitor outbound traffic for connections to its IPs, and review logs for any attempted accesses.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
google-live-maps.com — Suspicious Domain
AI description
PhishDestroy flags google-live-maps.com as a suspicious domain after Google Safe Browsing identified it as a social‑engineering threat.
AI summary
Overview PhishDestroy listed google-live-maps.com on 2026-10-28 following an intake that cited a Google Safe Browsing social‑engineering warning. The recorded page title is "Shared IP" and the site returned HTTP 200 on the same day. Google Safe Browsing marked the domain as a social‑engineering threat on 2026-10-28. Subsequent scans by VirusTotal, Cloudflare Radar and urlscan.io also reported malicious or phishing indicators. How the scam works The detections point to a phishing or social‑engineering risk, a category where attackers mimic trusted services to lure users into revealing credentials or personal data. Such schemes typically present a look‑alike login or request sensitive information, but no specific credential‑harvesting form was observed on the captured page. Because the page only displayed a generic title, the exact malicious payload cannot be confirmed from the available evidence. Evidence Google Safe Browsing flagged the domain for social engineering on 2026-10-28. VirusTotal recorded 17 detections out of 92 engines on 2026-10-28, with vendors such as BitDefender, ESET, Fortinet and others labeling it as phishing or malicious. Cloudflare Radar’s scan on 2026-10-28 assigned a phishing verdict and a malicious tag. urlscan.io’s machine‑learning engine gave a score of 74 and marked it malicious on 2026-10-26, while its overall verdict was clean. The external blocklist Phishunt also listed the domain, and PhishDestroy’s internal blocklist includes it as of 2026-10-27. OTX reported zero pulses on 2026-10-28. Infrastructure The domain was registered on 2026-02-21 through Purple IT Ltd and is set to expire on 2027-02-21. DNS records resolve to Cloudflare IPs 104.21.89.103 and 172.67.157.223, with AAAA records in Cloudflare’s network. The TLS certificate is issued by Let’s Encrypt (YE2), valid from 2026-10-15 to 2027-01-13, and DNSSEC is not enabled. Nameservers are elly.ns.cloudflare.com and emerson.ns.cloudflare.com. What to do Do not enter any Google credentials or personal data on this site; if you have already done so, change passwords and enable two‑factor authentication on the affected accounts. Report the domain to Google Safe Browsing and to your organization’s security team for blocking. Defenders should add google-live-maps.com to web‑filter blocklists, monitor outbound traffic for connections to its IPs, and review logs for any attempted accesses. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a178cc-7b72-709b-a990-a3680f783a30/ Cloudflare Radar report: https://radar.cloudflare.com/scan/de5c16a8-be00-42bc-a7d3-260600330d96 Stored capture screenshot: https://urlscan.io/screenshots/01a178cc-7b72-709b-a990-a3680f783a30.png Cloudflare Radar screenshot (2026-10-27T23:51:42Z): https://screenshots.phishdestroy.io/cf/de5c16a8-be00-42bc-a7d3-260600330d96.png URLScan screenshot (2026-02-21T15:42:29Z): https://screenshots.phishdestroy.io/us/019c80dd-c0b9-76ba-9127-5f16d327e882.png URLScan capture report: https://urlscan.io/result/019c80dd-c0b9-76ba-9127-5f16d327e882/ URLScan screenshot (2026-03-10T11:07:35Z): https://screenshots.phishdestroy.io/us/019cd76e-0d72-734a-ade8-f2f54e4f8f6c.png URLScan capture report: https://urlscan.io/result/019cd76e-0d72-734a-ade8-f2f54e4f8f6c/ URLScan screenshot (2026-06-19T20:16:54Z): https://screenshots.phishdestroy.io/us/019ee187-64e6-7724-ab67-c3e7e3fb6b42.png URLScan capture report: https://urlscan.io/result/019ee187-64e6-7724-ab67-c3e7e3fb6b42/ URLScan screenshot (2026-10-18T18:43:39Z): https://screenshots.phishdestroy.io/us/01a15053-85f7-70af-827f-9069784480e3.png URLScan capture report: https://urlscan.io/result/01a15053-85f7-70af-827f-9069784480e3/ URLScan screenshot (2026-10-19T04:54:38Z): https://screenshots.phishdestroy.io/us/01a15282-e44e-753d-a24c-a480fd78338b.png URLScan capture report: https://urlscan.io/result/01a15282-e44e-753d-a24c-a480fd78338b/ URLScan screenshot (2026-10-27T23:42:16Z): https://screenshots.phishdestroy.io/us/01a17fbe-109c-73e9-9236-94f93baca911.png URLScan capture report: https://urlscan.io/result/01a17fbe-109c-73e9-9236-94f93baca911/ VirusTotal report: https://www.virustotal.com/gui/domain/google-live-maps.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=google-live-maps.com Archived copy: https://web.archive.org/web/20261027233610/https://google-live-maps.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
Free email address used for contact Free email address used as technical contact Free email address used for contact administrator address The Tranco rank (how much traffic) is rather low The age of this site is (very) young. This website was reported by IPQS for phishing. This website has been classified as suspicious by IPQS
We found a valid SSL certificate DNSFilter labels this site as safe
Network Security Intelligence
Cloudflare Radar VerdictMalicious
Security threats Phishing Phishing
Questions about google-live-maps.com
Is google-live-maps.com legit?
PhishDestroy rates google-live-maps.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-27. Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-27 07:26 UTC. Retrieved (as stored): 2026-10-27 23:50 UTC. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is google-live-maps.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on google-live-maps.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used google-live-maps.com?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Social preview cardgoogle-live-maps.com: Google impersonation — Flagged by Google Safe Browsing, 17/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).v 5e3472d0ee8a
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement.
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 Detected2026-10-28
DOM Analysisanalyzed 2026-10-28score 98/1001 brand signal
Submitted URLhttp://google-live-maps.com/
Favicon Hash
Case ID
Observed page title
Shared IP
Automated brand references
Google
TLS Certificate
Issued by Let's Encrypt / YE2· stored validity ends in 52 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.89.103
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
elly.ns.cloudflare.com
emerson.ns.cloudflare.com
SOA
nsname: elly.ns.cloudflare.com
hostmaster: dns.cloudflare.com
serial: 2417591698
refresh: 10000
retry: 2400
expire: 604800
minttl: 1800
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-15 22:14:42
Valid until
2027-01-13 22:14:41
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbafd8eead01432547b1286fcf31b052614480e9a7aeabac8a7faf7ef118704e5Certificate names · 2 SANs
*.google-live-maps.com
google-live-maps.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:53 UTC.
Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Hours from detection to the first unavailable observation: 71
Recorded activity
7 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+247 d 15 h
Added to PhishDestroy+16 h 8 min
First abuse report sent+33 min
Reported 248 d 8 h after registration
Google Safe Browsing
Threat flag recorded
+58 h 54 min
Abuse report sent
PD-20261028-F28063 · Receipt 84005
abuse@purpleit.com
+4 min
URLScan
Page captured
+12 min
Cloudflare Radar
Phishing
+15 min
Wayback Machine
Page archived
same minute
Added to PhishDestroy
google-live-maps.com
+16 h 8 min
VirusTotal
17/92 engine detections
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 google-live-maps.com)
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
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 →
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.