Skip to security report
Analytics Dashboard
Domain security and threat intelligence
meine-app.login-utilizator.de favicon

meine-app.login-utilizator.de

In short

meine-app.login-utilizator.de is a credential phishing page detected by PhishDestroy on 2026-10-11. Risk: critical (100/100). Status: Last known active. Hosting: AS56971 Cloud. PhishDestroy sent 1 abuse report. VirusTotal: 6/92 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 6 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.

“Domain Default page”

Resolved IP
94.183.188.35
Registered
Oct 1, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 6/92 Automated brand label: Apple Young domain: 21 days old Google Safe Browsing: threat flag recorded
Oct 11, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@cloudbackbone.net. The latest stored availability evidence still shows the domain reachable; 11 days 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.

Elapsed since first report
11 days
Reports sent
1
Latest case ID
PD-20261011-8A6BCB
Current status
HTTP 200 at latest stored check
VirusTotal
6 / 92
engine detections
Google Safe Browsing
Flagged
Page captures
10
open gallery
Domain age
21 days
Reports sent
1
view timeline
Source evidenceVirusTotal 6 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

6 / 92 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

OTX

no community references

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
6 / 92
Page captures
10
Page captures Source results Registration record

PhishDestroy threat report

Overview

meine-app.login-utilizator.de is a credential phishing site that urlscan.io links to the Santander brand. It targets the bank's customers and anyone who receives a lure leading to a fake login. The hostname mixes German ("meine-app", my app) with Romanian ("login-utilizator", user login) to look like an official app sign-in. PhishDestroy first flagged it on 2026-10-11, and it was still online serving live content when last checked on 2026-10-19.

How the scam works

Victims usually arrive through a text message or email claiming a problem with their Santander account or app and urging them to sign in. The fake page collects the username, password and often one-time codes, then passes them to the operators. With those credentials they can log into the real account, approve transfers or enrol a new device before the victim notices. The browser tab reads "Domain Default page", which looks like an unconfigured server, while our classification and the scanner verdicts identify the site as Santander phishing.

Evidence

Several independent sources back the classification. Google Safe Browsing lists the site for social engineering, which triggers warnings in most major browsers. urlscan.io rated it malicious and detected Santander branding. On VirusTotal, 6 of 92 engines flagged it on 2026-10-12: alphaMountain.ai, CRDF, DNS8, Gridinsoft, SOCRadar and Webroot. That count is modest, so many security tools may still let the page load without warning. The domain is also listed on the PhishDestroy and PhishFeed blocklists.

Infrastructure

The site resolves to 94.183.188.35 on the AS56971 Cloud network in France. It uses a free, automatically issued Let's Encrypt certificate, so the padlock only means the connection is encrypted. It says nothing about who runs the site or whether it is really Santander.

What to do

If you entered your Santander credentials here, change your online banking password right away from the official app or the bank's real website. Call Santander using the number on your card so the bank can block suspicious transfers and remove any devices you don't recognise. Check recent transactions and payees, and change the password on any other service where you reused it. Treat any SMS codes you typed in as compromised, and be wary of follow-up calls from people posing as bank staff. Defenders should block the domain and its IP at mail and web gateways, and search logs for users who visited it.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-11T08:29:29Z

Observed: · Retrieved:

Uuid
01a12a14-aced-703b-9165-e7162b5209d0
Final url
https://meine-app.login-utilizator.de/portal/openlogin/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://meine-app.login-utilizator.de/portal/openlogin",
        "from": "http://meine-app.login-utilizator.de/portal/openlogin",
        "status": 307
    },
    {
        "to": "https://meine-app.login-utilizator.de/portal/openlogin/",
        "from": "https://meine-app.login-utilizator.de/portal/openlogin",
        "status": 301
    }
]
Ip
94.183.188.35
Contacted domains
[
    "ipwho.is"
]
Contacted IP addresses
[
    "104.20.44.133",
    "94.183.188.35"
]
Asns
[
    "13335",
    "56971"
]
Countries
[
    "FR"
]
Document hash
b9e7bbe69bbc8d92d0674c3e3ff1babc90cbe985860f11f7a60db8222f2f470a
Script hashes
[
    "910a4c1da6bf27aa5f5d8c4fedbf4b530a2bde5cb4354c60622d11615e073ba8"
]
Globals
[
    "RojaSync",
    "loginForm",
    "usernameInput",
    "passwordInput",
    "togglePassword",
    "eyeIcon",
    "submitBtn"
]
Storage keys
[
    "roja_visitor_id",
    "roja_client_geo",
    "roja_client_ip",
    "roja_online"
]
Tls
{
    "san": [
        "meine-app.login-utilizator.de"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "meine-app.login-utilizator.de",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-03T00:21:11Z",
    "valid_from": "2026-10-05T00:21:12Z"
}
Domain age days
4
Apex age days
10
Tls age days
6
Tls valid days
89
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "santander"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Santander"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "x-powered-by": "PleskLin"
}
Cloudflare Radar · 2026-10-12T10:41:49Z

Observed: · Retrieved:

Uuid
802d9ba6-426b-4c06-9507-92367a88de15
Final url
https://meine-app.login-utilizator.de/
Status
200
History
[
    {
        "url": "https://meine-app.login-utilizator.de/",
        "status": 200
    }
]
DOM structure hash
16ea3f6e8e1823e5e4a6efdb9e2f7bc0145b019122c05ec5457ce8172e330867
Document hash
6c703476d7302eb4ff2847f45852c235adfb9eacd32f39cf0610a818fa33738e
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "meine-app.login-utilizator.de",
        "type": "A",
        "value": "94.183.188.35"
    }
]
Dnssec valid
false
Ip
94.183.188.35
Registration record
{
    "updated": "2026-10-01T01:17:09Z",
    "nameservers": [
        "ignat.ns.cloudflare.com",
        "monroe.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-20T16:51:42Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 15,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "LevelBlue": "phishing",
    "Phishtank": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2026-10-01T00:00:00Z
First seen
2026-10-07T23:09:03Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "94.183.188.35"
    }
]
Dns at
2026-10-20T16:52:00Z
Jarm
29d3fd00029d29d00042d43d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "meine-app.login-utilizator.de"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6a66e53643d8aea9243b706505848618b09",
    "sha256": "c03e0217fb146c63b08e658038ca5799a4d9c2f819b9c1299a57ab753a3fd6bb",
    "subject": "meine-app.login-utilizator.de",
    "valid_to": "2027-01-03T00:21:11Z",
    "valid_from": "2026-10-05T00:21:12Z"
}

Questions about meine-app.login-utilizator.de

Is meine-app.login-utilizator.de legit?

No. PhishDestroy classifies meine-app.login-utilizator.de as a credential phishing page (risk: critical, 100/100); it was first detected on 2026-10-11. VirusTotal: 6/92 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 6 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Treat the site as unsafe.

Is meine-app.login-utilizator.de safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on meine-app.login-utilizator.de. 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 meine-app.login-utilizator.de?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded2026-10-11 08:30 UTC
StateStored capture
Position1 / 10
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Santander report ↗
Google Safe Browsing Flagged Social engineering checked Oct 22, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 11, 2026
Registrar (base domain) Unknown
Abuse contactabuse@cloudbackbone.net
Registration (base domain)login-utilizator.de · Created Oct 1, 2026 (21d · Very New!)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 11, 2026score 93/1004 brand signals
Submitted URLhttp://meine-app.login-utilizator.de/portal/openlogin
Favicon Hash
Case ID
Observed page title
Domain Default page
Automated brand references
Apple Google Santander Visa
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 72 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
94.183.188.35
Network ASN
AS56971
Organization
CGI GLOBAL LIMITED
Observed location
Paris, FR
Server header
nginx

Nameservers 2

  • ignat.ns.cloudflare.com
  • monroe.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-05 00:21:12
Valid until
2027-01-03 00:21:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc03e0217fb146c63b08e658038ca5799a4d9c2f819b9c1299a57ab753a3fd6bb
Certificate names · 1 SAN
  • meine-app.login-utilizator.de

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 94.183.188.35rapiddns.io

Latest Classified Outcome 2026-10-22 10:38:17 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 10:38:17 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:38:17 UTC last content: 2026-10-22 10:38:17 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 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
CRDF
DNS8
Gridinsoft
SOCRadar
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of meine-app.login-utilizator.de · checked Oct 12, 2026

99
Good
Performance
FCP
1.65s
First Contentful Paint
LCP
1.65s
Largest Contentful Paint
CLS
0.012
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.65s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history22

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    Reachable→Unavailable

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unavailable→Reachable

  5. Availability monitor · Recorded state

    Reachable→Unavailable

Earlier observations 17
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  5. Availability monitor · Recorded state

    Unavailable→Reachable

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unavailable→Reachable

  9. Availability monitor · Recorded state

    Reachable→Unavailable

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unavailable→Reachable

  12. Availability monitor · Recorded state

    Reachable→Unavailable

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    6/92 engine detections

    View source
  3. Abuse report sent

    PD-20261011-8A6BCB

    abuse@cloudbackbone.net
  4. Added to PhishDestroy

    meine-app.login-utilizator.de

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

meine-app.login-utilizator.de

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 6 det. ChainPatrol URLQuery Report stored Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261011-8A6BCB Recipient: abuse@cloudbackbone.net
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 meine-app.login-utilizator.de)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/meine-app.login-utilizator.de"
  title="PhishDestroy threat report for meine-app.login-utilizator.de"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>