VirusTotal
2 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“U.S. Bank Virtual File Assistant - Login”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@name.com.
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.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
2 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
15/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01 the domain usbank.xmldation.com returned HTTP status 302 according to the recorded HTTP check. A separate PageSpeed check on 2026-09-09 recorded a performance score of 92 for the same domain.
The domain was first observed on 2026-09-09, the same date as the SSL scan, which named Sectigo Limited / Sectigo Public Server Authentication CA DV R36 as issuer. VirusTotal, checked on 2026-09-22, reported 2 detections across 89 scanners, and the publisher-owned PhishDestroy catalogue listed the domain as of 2026-09-09.
The HTTP check, SSL scan and PhishDestroy listing carry different dates, so their records describe separate moments rather than one combined snapshot. VirusTotal's 2026-09-22 check falls later than the 2026-09-09 observations, which limits direct comparison between those source records.
Retain dated copies of each record for usbank.xmldation.com, including the HTTP check, SSL scan and PhishDestroy listing, so later observations can be compared against these baselines. Avoid submitting sensitive information during any review of usbank.xmldation.com, and compare subsequent records by their own collection dates.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
ns-cloud-d1.googledomains.comns-cloud-d2.googledomains.comns-cloud-d3.googledomains.comns-cloud-d4.googledomains.comLocation describes the IP network.
d36f185296dfdbf8051ebc62d4237612e86cf1aed6c0cb2d68820a51eae48678xmldation.comSaved 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 usbank.xmldation.com · checked Sep 9, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=/auth/oauth/authorize?client_id=xmldationclient&scope=openid&response_type=code&state=jVADOs1I&redirect_uri=https://usba
34.160.152.124.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
Unknown
probe_inconclusive
1→2
2→1
12→2
9→12
8→9
Reachable
14 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-20260909-B1AA3E Recipient: abuse@name.com 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 (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. 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