Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
amuentodenkkde--lineamenner.replit.app favicon

amuentodenkkde--lineamenner.replit.app

In short

PhishDestroy records amuentodenkkde--lineamenner.replit.app, whose captured page shows a Replit "This app isn't live yet" notice.

“Solicitud de Tarjeta de Crédito - Banco Pichincha”

Review the evidence
Registrar
Replit
Resolved IP
United States34.117.33.233Google LLC
Registered
Apr 16, 2021
First observed
Oct 29, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 14/92 Spamhaus DBL: DBL_ABUSED_PHISH Google Safe Browsing: threat flag recorded
VirusTotal
14 / 92
engine detections ·
Google Safe Browsing
Flagged
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
2,024 days
registered 2021-04-16 according to RDAP · source data differ
Oct 29, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records amuentodenkkde--lineamenner.replit.app, whose captured page shows a Replit "This app isn't live yet" notice.

Critical
Status
Last known active
VirusTotal
14 / 92
Hosting
United States34.117.33.233Google LLC
Registrar
Replit
Registered
Apr 16, 2021
Page captures
8
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page on amuentodenkkde--lineamenner.replit.app displays a Replit placeholder stating "This app isn't live yet," explaining that no Replit App could be found at this address and inviting the owner to publish the app to make it reachable. Two links offer guidance on publishing and hosting on Replit, and the page title "Solicitud de Tarjeta de Crédito - Banco Pichincha" differs from the placeholder content actually shown.

PhishDestroy's VirusTotal check of this domain found 14 of 92 engines flagging it, with 13 malicious and 1 suspicious verdicts. ESET labeled the domain phishing, while Netcraft labeled it malicious.

Source evidenceVirusTotal 14 / 92 · Google Safe Browsing: flagged 8 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
13
Suspicious
1
Undetected
33

Vendor labels

ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
CyRadar
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
suspicious
Kaspersky
phishing
LevelBlue
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

Sophos
information technology
Webroot
Phishing and Other Frauds
alphaMountain.ai
Information Technology, Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
web infrastructure

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
ec3ae2dfc6c55a2e109aff41a0e4b4c3
SHA-256
9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250
Subject
replit.app
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 13,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "suspicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Sophos": "information technology",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Information Technology, Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "web infrastructure"
}
Created
2021-04-16T00:00:00Z
Updated
2025-12-04T00:00:00Z
First seen
2026-10-28T22:55:07Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "34.117.33.233"
    }
]
Dns at
2026-10-29T16:55:57Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "replit.app",
        "*.replit.app"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "ec3ae2dfc6c55a2e109aff41a0e4b4c3",
    "sha256": "9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250",
    "subject": "replit.app",
    "valid_to": "2027-01-26T05:47:40Z",
    "valid_from": "2026-10-28T04:51:45Z"
}
Separate source record · 13 malicious + 1 suspicious / 92 · 2026-10-29 16:55:41 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-29T16:55:41Z
fetched_at
2026-10-29T19:42:20Z
stats
{"timeout":0,"harmless":45,"malicious":13,"suspicious":1,"undetected":33}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

cdac5a83-c1e1-4380-9cd6-775b9febd280

Final URL

https://amuentodenkkde--lineamenner.replit.app/

HTTP response

404

Navigation history

  • URL
    https://amuentodenkkde--lineamenner.replit.app/
    Status
    404

DOM structure hash

bebe73542fb033badbed0a2bc2f53b7deaa7a02e93da346597768b0124b34ee7

Document hash

7635515c8b5a86a74ecc1f676f409a931d49dc9307f7c9498ef6826c84dabb60

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    amuentodenkkde--lineamenner.replit.app
    Type
    A
    Value
    34.117.33.233

DNSSEC valid

No

IP address

127.0.1.17

127.0.1.17 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Nom-IQ Limited dba Com Laude
Registered
Updated
Expires
Nameservers
  • ns-cloud-b1.googledomains.com
  • ns-cloud-b2.googledomains.com
  • ns-cloud-b3.googledomains.com
  • ns-cloud-b4.googledomains.com
Original source fields · JSON
Uuid
cdac5a83-c1e1-4380-9cd6-775b9febd280
Final url
https://amuentodenkkde--lineamenner.replit.app/
Status
404
History
[
    {
        "url": "https://amuentodenkkde--lineamenner.replit.app/",
        "status": 404
    }
]
DOM structure hash
bebe73542fb033badbed0a2bc2f53b7deaa7a02e93da346597768b0124b34ee7
Document hash
7635515c8b5a86a74ecc1f676f409a931d49dc9307f7c9498ef6826c84dabb60
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "amuentodenkkde--lineamenner.replit.app",
        "type": "A",
        "value": "34.117.33.233"
    }
]
Dnssec valid
false
Ip
127.0.1.17

127.0.1.17 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Nom-IQ Limited dba Com Laude",
    "created": "2021-04-16T20:44:58Z",
    "updated": "2025-10-10T03:54:10Z",
    "expires": "2034-04-16T20:44:58Z",
    "nameservers": [
        "ns-cloud-b1.googledomains.com",
        "ns-cloud-b2.googledomains.com",
        "ns-cloud-b3.googledomains.com",
        "ns-cloud-b4.googledomains.com"
    ]
}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

DBL_ABUSED_PHISH

URLScan

Malicious

SHA-256 7e652fc5a7828485ec778f4f535b84a2ddd943a539f2a89343e12ae8c0928dec

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a187f2-6f60-721b-be87-8ded9e1580e9

Final URL

https://amuentodenkkde--lineamenner.replit.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://amuentodenkkde--lineamenner.replit.app/
    From
    http://amuentodenkkde--lineamenner.replit.app/
    Status
    307

IP address

34.117.33.233

Reverse DNS (PTR)

233.33.117.34.bc.googleusercontent.com

Contacted domains

  • fonts.gstatic.com
  • encrypted-tbn0.gstatic.com
  • replit-cdn.com
  • upload.wikimedia.org
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.38.131
  • 2a00:1450:4014:801::200e
  • 35.190.3.23
  • 2a02:ec80:600:ed1a::2:b
  • 2a00:1450:4014:801::200a
  • 34.117.33.233

Autonomous systems (ASN)

  • 15169
  • 396982
  • 14907

Server countries

  • US
  • IE

Document hash

d049dc8ef7a41a2db677ac15a17ccaacad2bb6aafead7f24ca1fabfd32a20c94

JavaScript globals

  • togglePasswordVisibility
  • handleSubmit

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

1

Certificate validity, days

90

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • bancopichincha
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Banco Pichincha
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Google Frontend
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=63072000; includeSubDomains
Original source fields · JSON
Uuid
01a187f2-6f60-721b-be87-8ded9e1580e9
Final url
https://amuentodenkkde--lineamenner.replit.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://amuentodenkkde--lineamenner.replit.app/",
        "from": "http://amuentodenkkde--lineamenner.replit.app/",
        "status": 307
    }
]
Ip
34.117.33.233
Ptr
233.33.117.34.bc.googleusercontent.com
Contacted domains
[
    "fonts.gstatic.com",
    "encrypted-tbn0.gstatic.com",
    "replit-cdn.com",
    "upload.wikimedia.org",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.38.131",
    "2a00:1450:4014:801::200e",
    "35.190.3.23",
    "2a02:ec80:600:ed1a::2:b",
    "2a00:1450:4014:801::200a",
    "34.117.33.233"
]
Asns
[
    "15169",
    "396982",
    "14907"
]
Countries
[
    "US",
    "IE"
]
Document hash
d049dc8ef7a41a2db677ac15a17ccaacad2bb6aafead7f24ca1fabfd32a20c94
Globals
[
    "togglePasswordVisibility",
    "handleSubmit"
]
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
1
Tls valid days
90
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "bancopichincha"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Banco Pichincha"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Google Frontend",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains"
}
Separate monitor record · 2026-10-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a187f2-6f60-721b-be87-8ded9e1580e9
score
100
malicious
true
result_at
2026-10-30T04:30:24Z
enriched_at
2026-10-30T09:11:45Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:24","urlscan_enriched_at":"2026-10-30 10:11:45"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

PhishDestroy DOM

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

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

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-29T15:20:18Z
source_timestamp
2026-10-29 16:20:18
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
amuentodenkkde--lineamenner.replit.app - Replit app not live yet
ai_description
PhishDestroy records amuentodenkkde--lineamenner.replit.app, whose captured page shows a Replit "This app isn't live yet" notice.
ai_summary
The captured page on amuentodenkkde--lineamenner.replit.app displays a Replit placeholder stating "This app isn't live yet," explaining that no Replit App could be found at this address and inviting the owner to publish the app to make it reachable. Two links offer guidance on publishing and hosting on Replit, and the page title "Solicitud de Tarjeta de Crédito - Banco Pichincha" differs from the placeholder content actually shown. PhishDestroy's VirusTotal check of this domain found 14 of 92 engines flagging it, with 13 malicious and 1 suspicious verdicts. ESET labeled the domain phishing, while Netcraft labeled it malicious.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 20:48:06
revision
5b748397b9245a064a7dbcb8af7e20b3574d8482effd508239cc2798085dc26a
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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: 23 fields

Mail configuration

SPF lookups
0

CAA records

Domain
amuentodenkkde--lineamenner.replit.app

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
5634

Page title and metadata

Page title
Solicitud de Tarjeta de Crédito - Banco Pichincha

Trackers

Requests
6
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    WikiMedia
    Company
    Wikimedia Foundation
    Country
    US
    Category
    Hosting
    Requests
    1

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
17
TLS
51
Waiting
5224
Connection
12
Download
1
Response time, ms
5305

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
16424
CO₂, grams
0.0006
Cleaner than, %
61

DNS servers

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

Cookies

Cookies
  • Name
    GAESA
  • Name
    WMF-Uniq
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

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://amuentodenkkde--lineamenner.replit.app

Page links

Internal links
1

HTTP headers

Response headers
Server
Google Frontend
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=63072000; includeSubDomains
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "amuentodenkkde--lineamenner.replit.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-29T13:41:50Z",
    "first": "2026-10-29T13:41:50Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 5634
}
Page title and metadata
{
    "title": "Solicitud de Tarjeta de Crédito - Banco Pichincha"
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "WikiMedia",
            "company": "Wikimedia Foundation",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
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": 17,
        "tls": 51,
        "wait": 5224,
        "connect": 12,
        "download": 1
    },
    "response_ms": 5305
}
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": 16424,
    "co2_grams": 0.0006,
    "cleaner_than": 61
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.32.107",
            "host": "ns-cloud-b1.googledomains.com"
        },
        {
            "ip": "216.239.38.107",
            "host": "ns-cloud-b4.googledomains.com"
        },
        {
            "ip": "216.239.36.107",
            "host": "ns-cloud-b3.googledomains.com"
        },
        {
            "ip": "216.239.34.107",
            "host": "ns-cloud-b2.googledomains.com"
        }
    ],
    "zone": "replit.app"
}
Cookies
{
    "cookies": [
        {
            "name": "GAESA"
        },
        {
            "name": "WMF-Uniq",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        }
    ]
}
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://amuentodenkkde--lineamenner.replit.app"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Google Frontend",
        "content-type": "text/html; charset=UTF-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about amuentodenkkde--lineamenner.replit.app

Is amuentodenkkde--lineamenner.replit.app legit?

PhishDestroy records amuentodenkkde--lineamenner.replit.app, whose captured page shows a Replit "This app isn't live yet" notice.

Is amuentodenkkde--lineamenner.replit.app safe to connect a wallet?

This report does not record which wallet requests amuentodenkkde--lineamenner.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 amuentodenkkde--lineamenner.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

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 8 captures

Cloudflare Radar 1 / 8 Used in the analysis Source file SHA-256: 02cfb2467b15224dd4b65b3b7d17c1d75906ea6bc87de632c0833b982c2b0049 SHA-256 of the prepared copy given to the model: 92e47d2e3c6926abebc167f1f2ef5387ccb661d5effc70e3fc2e69a4c817473b
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status404
Final URLhttps://amuentodenkkde--lineamenner.replit.app/
Position1 / 8
Open capture Source Report Wayback Download
All capture links and hashes (8)
Observed page title
Solicitud de Tarjeta de Crédito - Banco Pichincha
TLS Certificate
Issued by Google Trust Services / WR3 · stored validity ends in 86 days
amuentodenkkde--lineamenner.replit.app: Linea impersonation — Flagged by Google Safe Browsing, Spamhaus DBL, 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card amuentodenkkde--lineamenner.replit.app: Linea impersonation — Flagged by Google Safe Browsing, Spamhaus DBL, 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 792263785bb8

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Bancopichincha report ↗
Google Safe Browsing Flagged Social engineering checked Oct 31, 2026
IP Reputation United States34.117.33.233 abuse score 52/100 13 reports Fraud OrdersFTP Brute-ForcePhishingFraud VoIPEmail SpamPort ScanHackingSpoofingBrute-ForceBad Web Bot checked Oct 29, 2026 last reported
Registrar (base domain) Replit
Abuse contactabuse@replit.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for replit.app →
Registration (base domain)replit.app · Created Apr 16, 2021 — Expires Apr 16, 2034
HTTP Status301 Moved Permanently
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 0/100
Submitted URLhttp://amuentodenkkde--lineamenner.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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
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
Google Trust Services / WR3
Valid from
2026-10-28 04:51:45
Valid until
2027-01-26 05:47:40
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-29 14:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250
Certificate names · 1 SAN
  • replit.app

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

viewdns.info · 34.117.33.233rapiddns.io

Latest Classified Outcome 2026-10-31 23:03:50 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:03:50 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:03:50 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 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Fortinet
G-Data
Kaspersky
LevelBlue
Lionic
Netcraft
SOCRadar
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of amuentodenkkde--lineamenner.replit.app · checked Oct 29, 2026

100
Good
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.79 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://amuentodenkkde--lineamenner.replit.app/
Final URL: https://amuentodenkkde--lineamenner.replit.app/
Solicitud de Tarjeta de Crédito - Banco Pichincha
Response
HTTP 200
HTML body
16.0 KB
Compressed
4.7 KB
Links
2 internal · 0 external
Selected response headers
Cache-Control: private
Content-Type: text/html; charset=UTF-8
Server: Google Frontend
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Alt-Svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Cache-Control
private
Content-Type
text/html; charset=UTF-8
Date
Thu, 29 Oct 2026 13:42:58 GMT
Expires
Thu, 29 Oct 2026 13:42:58 GMT
Server
Google Frontend
Strict-Transport-Security
max-age=63072000; includeSubDomains
Transfer-Encoding
chunked
Via
1.1 google
X-Cloud-Trace-Context
6f2ebdec40e4265e7e4e84d1337b5c56;o=1

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details2

Availability observations

Last reachable 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: 7 SHA-256 hashes: 7 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 13:58 UTC.

Open this scan on URLScan 01a187f2-6f60-721b-be87-8ded9e1580e9 ↗

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

    redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected

    http_redirect

  4. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  5. Domain monitor · First collection record

    Reachable

All retained availability observations14

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:03:50.000000
    Evidence SHA-256
    02c8d0631720d5f5fd56c909c999f56e99270f712738f9c84bc46f976c7d681e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:03:50
    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:03:50.000000
    Evidence SHA-256
    02c8d0631720d5f5fd56c909c999f56e99270f712738f9c84bc46f976c7d681e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:03:50
    Evidence reason
    redirect
  3. 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 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  4. 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:04:14.000000
    Evidence SHA-256
    ec38e7ae736dae94a682def7c762a7a741c2de010278ddf7345b20b1453c7fc0
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:04:14
    Evidence reason
    redirect
  5. 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:04:14.000000
    Evidence SHA-256
    ec38e7ae736dae94a682def7c762a7a741c2de010278ddf7345b20b1453c7fc0
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:04:14
    Evidence reason
    redirect
  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 00:58:01.000000
    Evidence SHA-256
    936df30056554ef015bdf3719fe00df2f1b81bd5053c733826cc4a2f5798ca96
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 00:58:01
    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 00:58:01.000000
    Evidence SHA-256
    936df30056554ef015bdf3719fe00df2f1b81bd5053c733826cc4a2f5798ca96
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 00:58:01
    Evidence reason
    redirect
  8. 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 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  9. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    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-30 13:10:23.000000
    Evidence SHA-256
    293907de2cc34a6f9cbc45ce29b142ad94c063a9c4bd86972d9df17cb7f2299d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 13:10:23
    Evidence reason
    redirect
  10. 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-30 13:10:23.000000
    Evidence SHA-256
    293907de2cc34a6f9cbc45ce29b142ad94c063a9c4bd86972d9df17cb7f2299d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 13:10:23
    Evidence reason
    redirect
  11. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    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-30 01:23:29.000000
    Evidence SHA-256
    40c0fbefa660576b1fec5b1b30f6f75b425b8fefef1c66106738a6e78ae9f15b
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 01:23:29
    Evidence reason
    redirect
  12. 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-30 01:23:29.000000
    Evidence SHA-256
    40c0fbefa660576b1fec5b1b30f6f75b425b8fefef1c66106738a6e78ae9f15b
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 01:23:29
    Evidence reason
    redirect
  13. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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 14:56:59.000000
    Evidence SHA-256
    7948939703c31df4a8d7803c0865b0c1a4a84251f2a8054fbfa4867cdb98ab6e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 14:56:59
    Evidence reason
  14. 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 14:56:59.000000
    Evidence SHA-256
    7948939703c31df4a8d7803c0865b0c1a4a84251f2a8054fbfa4867cdb98ab6e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 14:56:59
    Evidence reason

Threat Response Pipeline

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

Recorded events: 13. 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
    amuentodenkkde--lineamenner.replit.app detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Google Safe Browsing · Cloudflare Radar: Malicious · Automated brand label: Linea · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 11 of 11
  • Spamhaus DBL
    Spamhaus DBL recorded: DBL_ABUSED_PHISH
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 14/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Phishing, Security threats
  • Automated brand label: Linea
    Collector label, not confirmed by a page check.
  • 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

6 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. VirusTotal

    14/92 engine detections

    View source
  4. Added to PhishDestroy

    amuentodenkkde--lineamenner.replit.app

    View source
  5. URLScan

    Page captured

    View source
  6. Wayback Machine

    Page archived

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

amuentodenkkde--lineamenner.replit.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 14 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Certificate hostname mismatch CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
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
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?

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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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 amuentodenkkde--lineamenner.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

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

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.

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