Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
prestamosubii--ceditopersonal.replit.app favicon

prestamosubii--ceditopersonal.replit.app

In short

PhishDestroy stores a record for prestamosubii--ceditopersonal.replit.app. Source observations are dated separately; missing checks do not establish safety.

“Ubiipagos”

Registrar
Replit
Resolved IP
United States34.117.33.233Google LLC
Registered
Apr 16, 2021
First observed
Oct 29, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 4/92 Stored blocklist matches: 2
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL
URLScan
engine verdict · score 99
Page captures
open gallery
Domain age
registered 2021-04-16 according to RDAP · source data differ
Oct 29, 2026
X Telegram API

Questions about prestamosubii--ceditopersonal.replit.app

Is prestamosubii--ceditopersonal.replit.app legit?

PhishDestroy stores a record for prestamosubii--ceditopersonal.replit.app. Source observations are dated separately; missing checks do not establish safety.

Is prestamosubii--ceditopersonal.replit.app safe to connect a wallet?

This report does not record which wallet requests prestamosubii--ceditopersonal.replit.app 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.

What should I do if I used prestamosubii--ceditopersonal.replit.app?

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.

Explore

Source evidenceVirusTotal 4 / 92 6 sources

VirusTotal

4 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
52
Malicious
4
Suspicious
0
Undetected
36

Vendor labels

CRDF
malicious
LevelBlue
phishing
ChainPatrol
malicious
alphaMountain.ai
malicious

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Information Technology, Malicious (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    34.117.33.233

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84

Certificate

Subject alternative names
  • replit.app
  • *.replit.app
Issuer
Google Trust Services / WR3
Serial
b3df8d4daf091430a5fcdb9944aa352
SHA-256
4a74494d584027de8f1b50d93d1683733368fbaea4298191709beefd53e0b0ae
Subject
replit.app
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "CRDF": "malicious",
    "LevelBlue": "phishing",
    "ChainPatrol": "malicious",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Information Technology, Malicious (alphaMountain.ai)"
}
Created
2021-04-16T00:00:00Z
Updated
2025-12-04T00:00:00Z
First seen
2026-10-28T03:33:27Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "34.117.33.233"
    }
]
Dns at
2026-10-28T03:33:35Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "replit.app",
        "*.replit.app"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "b3df8d4daf091430a5fcdb9944aa352",
    "sha256": "4a74494d584027de8f1b50d93d1683733368fbaea4298191709beefd53e0b0ae",
    "subject": "replit.app",
    "valid_to": "2026-12-01T12:25:50Z",
    "valid_from": "2026-09-02T11:30:15Z"
}
Separate source record · 4 malicious + 0 suspicious / 92 · 2026-10-28 03:05:20 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-28T03:05:20Z
fetched_at
2026-10-29T00:42:11Z
stats
{"timeout":0,"harmless":52,"malicious":4,"suspicious":0,"undetected":36}

URLScan

Malicious · engine verdict · score 99

SHA-256 7071973040d669433c320de735f59a73651488423260dd6dcca5a2253e226c6b

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1850e-8ace-7022-862e-ba1a58214f46

Final URL

https://prestamosubii--ceditopersonal.replit.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://prestamosubii--ceditopersonal.replit.app/
    From
    http://prestamosubii--ceditopersonal.replit.app/
    Status
    307

IP address

34.117.33.233

Reverse DNS (PTR)

233.33.117.34.bc.googleusercontent.com

Contacted domains

  • replit-cdn.com
  • ubiionline.ubiipagos.com

Contacted IP addresses

  • 35.190.3.23
  • 34.117.33.233

Autonomous systems (ASN)

  • 396982

Server countries

  • US

Document hash

80e372bc16ed9403d3f5db7d49246f040bbbf027793df990ca7ae2a6935ea00a

Cookies

  • GAESA

TLS session and certificate

Subject alternative names
  • replit.app
  • *.replit.app
Cipher
AES_128_GCM
Issuer
WR3
Subject
replit.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Differs from the registration date in RDAP (2021-04-16), which gives 2021 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Registered domain age, days

0

Differs from the registration date in RDAP (2021-04-16), which gives 2021 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Certificate age, days

0

Certificate validity, days

90

Page requests

3

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Google Frontend
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.2.0RC7
Strict-transport-security
max-age=63072000; includeSubDomains
Original source fields · JSON
Uuid
01a1850e-8ace-7022-862e-ba1a58214f46
Final url
https://prestamosubii--ceditopersonal.replit.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://prestamosubii--ceditopersonal.replit.app/",
        "from": "http://prestamosubii--ceditopersonal.replit.app/",
        "status": 307
    }
]
Ip
34.117.33.233
Ptr
233.33.117.34.bc.googleusercontent.com
Contacted domains
[
    "replit-cdn.com",
    "ubiionline.ubiipagos.com"
]
Contacted IP addresses
[
    "35.190.3.23",
    "34.117.33.233"
]
Asns
[
    "396982"
]
Countries
[
    "US"
]
Document hash
80e372bc16ed9403d3f5db7d49246f040bbbf027793df990ca7ae2a6935ea00a
Cookies
[
    "GAESA"
]
Tls
{
    "san": [
        "replit.app",
        "*.replit.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR3",
    "subject": "replit.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-26T05:47:40Z",
    "valid_from": "2026-10-28T04:51:45Z"
}
Domain age days
0

Differs from the registration date in RDAP (2021-04-16), which gives 2021 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Apex age days
0

Differs from the registration date in RDAP (2021-04-16), which gives 2021 days on the scan date 2026-10-29. The two sources disagree; both values are kept as recorded.

Tls age days
0
Tls valid days
90
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Google Frontend",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.2.0RC7",
    "strict-transport-security": "max-age=63072000; includeSubDomains"
}
Separate monitor record · 2026-10-29 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1850e-8ace-7022-862e-ba1a58214f46
score
0
malicious
false
result_at
2026-10-29T04:30:24Z
enriched_at
2026-10-29T09:14:37Z
source_timestamps
{"urlscan_result_at":"2026-10-29 05:30:24","urlscan_enriched_at":"2026-10-29 10:14:37"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-29T03:20:22Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-29T03:20:22Z
source_timestamp
2026-10-29 04:20:22
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
prestamosubii--ceditopersonal.replit.app

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
Ubiipagos

Trackers

Requests
2

Forms and mixed content

Scripts without SRI
  • https://replit-cdn.com/replit-pill/replit-pill.global.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
330
TLS
313
Waiting
880
Connection
76
Download
0
Response time, ms
1599

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
8450
CO₂, grams
0.0003
Cleaner than, %
75

DNS servers

Nameservers
  • IP address
    216.239.34.107
    Host
    ns-cloud-b2.googledomains.com
  • IP address
    216.239.36.107
    Host
    ns-cloud-b3.googledomains.com
  • IP address
    216.239.32.107
    Host
    ns-cloud-b1.googledomains.com
  • IP address
    216.239.38.107
    Host
    ns-cloud-b4.googledomains.com
DNS zone
replit.app

Cookies

Cookies
  • Name
    GAESA

Location

IP address
34.117.33.233
ASN
396982
Organization
Google LLC
City
Kansas City
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
replit.app

DNS records

A
  • 34.117.33.233

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains
Observation
HSTS header does not contain the preload directive.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
34.117.33.233
IP version
4

Redirects

Redirect chain
  • https://prestamosubii--ceditopersonal.replit.app

Page links

Internal links
2

HTTP headers

Response headers
Server
Google Frontend
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.2.0RC7
Strict-transport-security
max-age=63072000; includeSubDomains
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "prestamosubii--ceditopersonal.replit.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "title": "Ubiipagos"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "no_sri": [
        "https://replit-cdn.com/replit-pill/replit-pill.global.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 330,
        "tls": 313,
        "wait": 880,
        "connect": 76,
        "download": 0
    },
    "response_ms": 1599
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 8450,
    "co2_grams": 0.0003,
    "cleaner_than": 75
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.107",
            "host": "ns-cloud-b2.googledomains.com"
        },
        {
            "ip": "216.239.36.107",
            "host": "ns-cloud-b3.googledomains.com"
        },
        {
            "ip": "216.239.32.107",
            "host": "ns-cloud-b1.googledomains.com"
        },
        {
            "ip": "216.239.38.107",
            "host": "ns-cloud-b4.googledomains.com"
        }
    ],
    "zone": "replit.app"
}
Cookies
{
    "cookies": [
        {
            "name": "GAESA"
        }
    ]
}
Location
{
    "ip": "34.117.33.233",
    "asn": "396982",
    "org": "Google LLC",
    "city": "Kansas City",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "replit.app"
}
DNS records
{
    "A": [
        "34.117.33.233"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains",
    "message": "HSTS header does not contain the preload directive."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "34.117.33.233",
    "family": 4
}
Redirects
{
    "chain": [
        "https://prestamosubii--ceditopersonal.replit.app"
    ]
}
Page links
{
    "internal_count": 2
}
HTTP headers
{
    "headers": {
        "server": "Google Frontend",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "PHP/8.2.0RC7",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
    }
}
Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 2 captures

All capture links and hashes (2)
Observed page title
Ubiipagos
TLS Certificate
Issued by WR3 · stored validity ends in 86 days
prestamosubii--ceditopersonal.replit.app: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 66/100 (high).
Social preview card prestamosubii--ceditopersonal.replit.app: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 66/100 (high). v 7da6de3a57e0

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Reputation United States34.117.33.233 abuse score 42/100 11 reports Fraud OrdersPhishingEmail SpamPort ScanHackingSpoofingBad Web Bot checked Oct 29, 2026 last reported
Registrar (base domain) Replit
Abuse contactabuse@replit.com
Registration (base domain)replit.app · Created Apr 16, 2021 — Expires Apr 16, 2034
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 0/100
Submitted URLhttp://prestamosubii--ceditopersonal.replit.app/
Favicon Hash
ICANN OVERSIGHT Registration: replit.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain replit.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States34.117.33.233
Network ASN
AS396982
AS name
GOOGLE-CLOUD-PLATFORM - Google LLC, US
Organization
Google LLC
Observed location
United StatesKansas City, US
Server header
Google Frontend

Location describes the IP network.

TLS certificate

Issuer
WR3
Valid from
2026-10-28 04:51:45
Valid until
2027-01-26 05:47:40
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint4a74494d584027de8f1b50d93d1683733368fbaea4298191709beefd53e0b0ae
Certificate names · 2 SANs
  • replit.app
  • *.replit.app

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

Latest Classified Outcome 2026-10-31 23:08:26 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-31 23:08:26 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:08:26 UTC last content: 2026-10-30 11:06:34 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.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
ChainPatrol
alphaMountain.ai
CRDF
LevelBlue
SOCRadar
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.

Captured network requests

Network requests: 3 SHA-256 hashes: 2 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 01:52 UTC.

Open this scan on URLScan 01a1850e-8ace-7022-862e-ba1a58214f46 ↗

Stored observation history5

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

    redirected

    http_redirect

  2. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations17

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.

  1. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:26.000000
    Evidence SHA-256
    cd1c18302df55d140420dbfc531786579e7468f43aab7b64257277c0650bde4b
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:08:26
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:26.000000
    Evidence SHA-256
    cd1c18302df55d140420dbfc531786579e7468f43aab7b64257277c0650bde4b
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:08:26
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:12.000000
    Evidence SHA-256
    165382644fbea6ac256e5a2ffc7cea918fb23e123cddf462c4529e7e216cf0e7
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:09:12
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:12.000000
    Evidence SHA-256
    165382644fbea6ac256e5a2ffc7cea918fb23e123cddf462c4529e7e216cf0e7
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:09:12
    Evidence reason
    redirect
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  6. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:17.000000
    Evidence SHA-256
    1b35fa4331c569de7e08d6e340c2aab2369872b08c7eb8d1232dc1ed4396ae52
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 03:30:17
    Evidence reason
    redirect
  7. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:17.000000
    Evidence SHA-256
    1b35fa4331c569de7e08d6e340c2aab2369872b08c7eb8d1232dc1ed4396ae52
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 03:30:17
    Evidence reason
    redirect
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:34.000000
    Evidence SHA-256
    3ccb52933464b2822c7bb1da22bf0c82a6847ab65b91722b975000c62fc0d7ba
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:34
    Evidence reason
    alive_content
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:34.000000
    Evidence SHA-256
    3ccb52933464b2822c7bb1da22bf0c82a6847ab65b91722b975000c62fc0d7ba
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:34
    Evidence reason
    alive_content
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:06:55.000000
    Evidence SHA-256
    5d46d12dba288e942e1f434f803d651ce2fbfadaea50dd0398cb318c28cfcf60
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:06:55
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:06:55.000000
    Evidence SHA-256
    5d46d12dba288e942e1f434f803d651ce2fbfadaea50dd0398cb318c28cfcf60
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:06:55
    Evidence reason
    alive_content
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:17.000000
    Evidence SHA-256
    c167568880c026e90016732807fd66afc6d85e64dd1889eb2d5d521d4d665948
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:17
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:17.000000
    Evidence SHA-256
    c167568880c026e90016732807fd66afc6d85e64dd1889eb2d5d521d4d665948
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:17
    Evidence reason
    alive_content
  15. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  16. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:29:23.000000
    Evidence SHA-256
    ace711dba08afe5264baa0fa39be59db3846b9da6079af914daeca54bbd106b2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:29:23
    Evidence reason
  17. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:29:23.000000
    Evidence SHA-256
    ace711dba08afe5264baa0fa39be59db3846b9da6079af914daeca54bbd106b2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:29:23
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    prestamosubii--ceditopersonal.replit.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · VirusTotal · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. Added to PhishDestroy

    prestamosubii--ceditopersonal.replit.app

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    4/92 engine detections

    View source
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Check for cloaking

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

prestamosubii--ceditopersonal.replit.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

Select 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.

97-country directory

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.

  • 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

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 prestamosubii--ceditopersonal.replit.app)
  • 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

Stay Informed, Stay Safe

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

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.

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.

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/prestamosubii--ceditopersonal.replit.app"
  title="PhishDestroy threat report for prestamosubii--ceditopersonal.replit.app"
  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>