VirusTotal
3 / 93 engine detections
PhishDestroy first recorded guarda.broker on 2026-02-15. Stored VirusTotal result: 3/93 engines flagged.
“Guarda Wallet - Restore from Backup ☑️”
Recorded source summary
PhishDestroy stores a record for guarda.broker. Source observations are dated separately; missing checks do not establish safety.
A reviewed analysis is not available for this text revision. Consult the dated source records below.
3 / 93 engine detections
Suspicious
Open reportObserved: · Retrieved:
| Uuid | 09d9dba5-75f2-4a14-9a3c-701e42520ffb |
|---|---|
| Final url | https://guarda.broker/ |
| Status | 200 |
| History | [
{
"url": "https://guarda.broker/",
"status": 200
}
] |
| DOM structure hash | ecfdf696a03124ad76ddc6c2514900913c6c6188d04a69e272d549586c404bba |
| Document hash | 214f2bc941eca10ea94498fb50757578ecbf511e920103dd2940564d6b914219 |
| Domain risks | [
"Newly Seen Domains",
"Security Risks"
] |
| DNS records | [
{
"name": "guarda.broker",
"type": "A",
"value": "31.31.196.49"
},
{
"name": "guarda.broker",
"type": "AAAA",
"value": "2a00:f940:2:2:1:1:0:275"
},
{
"name": "www.guarda.broker",
"type": "A",
"value": "31.31.196.49"
},
{
"name": "www.guarda.broker",
"type": "AAAA",
"value": "2a00:f940:2:2:1:1:0:275"
}
] |
| Dnssec valid | false |
| Ip | 31.31.196.49 |
| Registration record | {
"registrar": "URL Solutions, Inc.",
"created": "2026-02-04T05:57:05Z",
"updated": "2026-03-02T06:52:05Z",
"expires": "2027-02-04T05:57:05Z",
"nameservers": [
"ns1.hosting.reg.ru",
"ns2.hosting.reg.ru"
]
} |
Malicious · engine verdict · score 82
Open reportObserved: · Retrieved:
| Uuid | 019c61b9-510f-74df-bf63-7c651189f1d4 |
|---|---|
| Final url | https://guarda.broker/ |
| Status | 200 |
| Ip | 31.31.196.49 |
| Ptr | server275.hosting.reg.ru |
| Contacted domains | [
"www.guarda.broker"
] |
| Contacted IP addresses | [
"31.31.196.49"
] |
| Asns | [
"197695"
] |
| Countries | [
"RU"
] |
| Linked domains | [
"www.guarda.broker",
"forms.gle",
"support.www.guarda.broker",
"apps.apple.com",
"play.google.com",
"chromewebstore.google.com",
"www.trustpilot.com",
"sourceforge.net",
"www.investopedia.com",
"coinjournal.net",
"99bitcoins.com",
"www.newsbtc.com",
"coinpaper.com",
"altcoinlog.com",
"invezz.com",
"cryptodaily.co.uk",
"cryptonewsland.com",
"github.com"
] |
| Social | [
"https://github.com/guardaco/guarda-desktop-releases/releases/download/v1.0.20/Guarda-1.0.20.dmg",
"https://github.com/guardaco/guarda-desktop-releases/releases/download/v1.0.20/Guarda_1.0.20_amd64.deb",
"https://github.com/guardaco/guarda-desktop-releases/releases/download/v1.0.20/Guarda-1.0.20.AppImage"
] |
| Document hash | 214f2bc941eca10ea94498fb50757578ecbf511e920103dd2940564d6b914219 |
| Script hashes | [
"a3cf00c109d907e543bc4f6dbc85eb31068f94515251347e9e57509b52ee3d74",
"c57339c3fa16b1d69d9a6b46749a8139ef8d4fc9bbfe48144ff897aa7d4222ec",
"5c73435feaf6255c0ad0c40579285b34e2f62c3ab060d75b5b2603f257b2f3f0",
"09036b5ad63c4f3944cbe80da6f4b91064921420704fca3dab09340062c0a718",
"319c3f5b23750826c879ca86c21a31af16658beafb2d5969abb09e2b023df47d",
"3d9120fa621da6d613c1698b7014ec6bdf4620366e8f2b7b547059f4b6f6272b",
"7b5f486c0fd3e57fcc6fd05a2ba73c88ae929490336f22f4d0feed3c1dd37421",
"6d4cb67a77ccaac1eb6226ad28e5c991a57a03a8aea99e85523b7e0df6694770",
"20193736d900f0b602a678f804676349764578ab2adcd07ffebb6d06df1afd96"
] |
| Globals | [
"crashReport",
"$",
"jQuery",
"e",
"t",
"Fuse",
"lottie-player",
"reactiveElementVersions",
"litHtmlVersions",
"litElementVersions",
"LottieInteractivity",
"blockKeys",
"lazySizes",
"axios",
"FLETCHER",
"BUY_SELL",
"GUARDARIAN",
"SIMPLEX"
] |
| Tls | {
"san": [
"www.guarda.broker",
"autodiscover.guarda.broker",
"mail.guarda.broker",
"owa.guarda.broker",
"guarda.broker"
],
"cipher": "AES_256_GCM",
"issuer": "GlobalSign GCC R3 DV TLS CA 2020",
"subject": "www.guarda.broker",
"protocol": "TLS 1.3",
"valid_to": "2026-09-06T06:40:49Z",
"valid_from": "2026-02-04T06:40:49Z"
} |
| Domain age days | 11 |
| Apex age days | 11 |
| Tls age days | 11 |
| Tls valid days | 214 |
| Requests | 94 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-0.1.0-1-d9114fd"
],
"score": 82,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html",
"strict-transport-security": "max-age=31536000;"
} |
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
checked — no detections recorded
Open reportno community references
Open reportNo threat flag
Open reportCheck recorded; verdict not retained
Open report75 / 100 · heuristic score · 12 brand references · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
PhishDestroy rates guarda.broker as critical risk (75/100) from the recorded evidence; it was first recorded on 2026-02-15. Stored VirusTotal result: 3/93 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
This report does not record which wallet requests guarda.broker makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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.
Checked, no match
Last checked
cb623a378249717f76161d95a74edbb761bd1ec728ac8361211ce272ed9031a8 · 237795 bytes ab0b04eb564beb55ab76c6fbda7eb2cbf2eb2ab3025755ed09ec60a1735d62fd · 142833 bytes e3fe6adf180c19195483180eb65d7f2593e1238402d3e8d479426e2b5b07a697 · 142571 bytes e3fe6adf180c19195483180eb65d7f2593e1238402d3e8d479426e2b5b07a697 · 142571 bytes f9dd28c373111cafa6ff3b7dcbe56c321b8825e622685a5cb5bf20639f75c523 · 142772 bytes 851c618930c736d1b65ef3f3adff8c0cf35438b6f3da620bc1f8c78d1f60dd14 · 620769 bytes 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.
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.
ns2.hosting.reg.ruLocation describes the IP network.
389916f4bbdcb9eb8c8d3488261ba966baa5da17ff1774e060cf9fa575283203autodiscover.guarda.brokermail.guarda.brokerowa.guarda.brokerwww.guarda.brokerSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
autodiscover.guarda.brokerDomain recordmail.guarda.brokerDomain recordowa.guarda.brokerDomain recordwww.guarda.brokerDomain recordPHP is a general-purpose scripting language used for web development.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 94 SHA-256 hashes: 91 URLScan scan:
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 06:17 UTC.
Open this scan on URLScan 019c61b9-510f-74df-bf63-7c651189f1d4 ↗
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/09d9dba5-75f2-4a14-9a3c-701e42520ffb
Source: domain_monitor. This stored snapshot does not establish current availability.
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
guarda.broker
View sourcePD-20260215-151BBA · Receipt 13606
Page captured
View sourceWe 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Reported by 1 community member, first seen Feb 15, 2026
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
guarda.broker PD-20260215-151BBA Recipient: abuse@pananames.com Policy Violations: Section 3.1 of AUP: The domain guarda.broker is engaged in phishing activities, which directly contravenes the prohibition against illegal activities and fraud. Section 5.2 of TOS: The ongoing use of this domain for deceptive practices violates the terms that reserve the right to suspend or terminate services for such violations. Applicable Laws (Unknown): Computer Fraud and Abuse Act (CFAA) - 18 U.S.C. § 1030: This federal law prohibits unauthorized access to computers and the use of such access to commit fraud. Wire Fraud - 18 U.S.C. § 1343: This statute criminalizes schemes to defraud using electronic communications, which applies to the phishing activities associated with this domain. CAN-SPAM Act - 15 U.S.C. § 7701: This law regulates commercial email and prohibits misleading headers and deceptive subject lines, relevant in the context of phishing emails sent from this domain. Regulatory Note: Failure to take immediate action against this domain may result in liability under applicable laws and could lead to regulatory scrutiny. Prompt compliance is essential to mitigate potential legal repercussions.
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.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
Template-based draft • optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
guarda.broker)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.
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.