VirusTotal
6 / 89
“XMR Bridge — Private Swaps”
The sent-report ledger records the first outgoing report at .
The recorded recipient is jonathan-crawford36@swiftfynd.net.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
6 / 89
DBL_SPAM
checked — no detections recorded
Report4 community references
Reportprovider verdict: clean
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
Reportxmrbridger.com returned HTTP status 200 on 2026-10-01, a dated response recorded during the HTTP check. The domain was first observed on 2026-09-12, and its registration date is listed as 2026-07-20 by the registrar PDR Ltd. d/b/a PublicDomainRegistry.com.
The HTTP check on 2026-10-01 recorded status 200 for xmrbridger.com, while the first observation date is 2026-09-12. On 2026-09-12, OTX recorded 3 pulses, and the PhishDestroy internal listing was also recorded as true. VirusTotal, checked on 2026-09-19, reported 6 detections across 89 scanners, with observation time known set to false. The SSL scan on 2026-09-12 identified the issuer as Google Trust Services / WE1, and the PageSpeed check on the same date returned a performance score of 90.
The OTX and PhishDestroy records share the 2026-09-12 observation date, so they describe the same point in time, whereas the VirusTotal check on 2026-09-19 and the HTTP check on 2026-10-01 fall later. Because these named sources were captured on different dates, their values should be compared as separate snapshots rather than treated as one synchronized measurement. The differing dates mean a reader can track change over time without assuming that any single record describes the domain at another source's timestamp.
Retain the dated records for xmrbridger.com, including the HTTP, OTX, VirusTotal, SSL and PageSpeed observations, so later checks can be compared against the same source names and dates. When reviewing xmrbridger.com, compare each new observation with the prior dated value from the same source instead of mixing sources. Avoid submitting sensitive information during any review of xmrbridger.com until the recorded observations have been assessed against your own requirements.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.18.0 (Ubuntu)Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.18.0 (Ubuntu)
Edge-IP reputation is not attributed to this domain.
anderson.ns.cloudflare.comtess.ns.cloudflare.comLocation describes the IP network.
a19e4eb2fa5fbb15d04628dc0b8eb1e83d1ad993d2c45368260cb917a4de2413Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of xmrbridger.com · checked Sep 12, 2026
188.114.96.3. 13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
PD-20260912-B2A081 Recipient: jonathan-crawford36@swiftfynd.net Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (SC): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and SC's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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