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

materimelos04545040.vercel.app

In short

PhishDestroy stores a record for materimelos04545040.vercel.app. Source observations are dated separately; missing checks do not establish safety.

“L1staa de foo7os”

Registrar
United StatesVercel
Resolved IP
United States216.198.79.67CYPRESS COMMUNICATIONS, LLC · CDN
First observed
Oct 23, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 12/92 Stored blocklist matches: 1
VirusTotal
engine detections ·
Blocklist matches
PhishFeed
URLQuery
detections
URLScan
engine verdict · score 99
Page captures
open gallery
Oct 23, 2026 CDN
X Telegram API

Questions about materimelos04545040.vercel.app

Is materimelos04545040.vercel.app legit?

PhishDestroy stores a record for materimelos04545040.vercel.app. Source observations are dated separately; missing checks do not establish safety.

Is materimelos04545040.vercel.app safe to connect a wallet?

This report does not record which wallet requests materimelos04545040.vercel.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 materimelos04545040.vercel.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 12 / 92 7 sources

VirusTotal

12 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
12
Suspicious
0
Undetected
33

Vendor labels

ESET
phishing
Ermes
phishing
G-Data
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
MalwareURL
phishing

Reputation score

0

Tags

  • hex
  • dga

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.195
  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.195

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.vercel.app
Issuer
Google Trust Services / WR1
Serial
f7911168ffa7d0f4135e24792e7a52a8
SHA-256
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Subject
*.vercel.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "Ermes": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "MalwareURL": "phishing"
}
Reputation
0
Tags
[
    "hex",
    "dga"
]
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2026-10-17T10:53:21Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.195"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.195"
    }
]
Dns at
2026-10-19T10:26:51Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 12 malicious + 0 suspicious / 92 · 2026-10-19 10:26:39 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-19T10:26:39Z
fetched_at
2026-10-23T02:25:03Z
stats
{"timeout":0,"harmless":47,"malicious":12,"suspicious":0,"undetected":33}

URLScan

Malicious · engine verdict · score 99

SHA-256 be932e6d11b6c36289dc89cea1f450abc7953e6a5fad6daf76c35062e7736db1

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1664d-ed87-75bc-b8ae-5d3018d53627

Final URL

https://materimelos04545040.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://materimelos04545040.vercel.app/
    From
    http://materimelos04545040.vercel.app/
    Status
    307

IP address

64.29.17.3

Contacted domains

  • ps.eyeota.net
  • cm.g.doubleclick.net
  • ups.analytics.yahoo.com
  • match.adsrvr.org
  • pixel.onaudience.com
  • tags.crwdcntrl.net
  • t.dtscout.com
  • bcp.crwdcntrl.net
  • i.simpli.fi
  • d.agkn.com
  • aa.agkn.com
  • px.ads.linkedin.com
  • maxcdn.bootstrapcdn.com
  • i.postimg.cc
  • d.turn.com
  • um.simpli.fi
  • ssc-cms.33across.com
  • px.mountain.com
  • secure.adnxs.com
  • dp1.33across.com
  • idsync.rlcdn.com
  • dp2.33across.com
  • de.tynt.com
  • ib.adnxs.com
  • target.digitalaudience.io
  • cms.analytics.yahoo.com
  • t.dtscdn.com
  • ic.tynt.com
  • p.mrktmtrcs.net
  • cdn.tynt.com

Contacted IP addresses

  • 52.22.182.118
  • 184.194.37.13
  • 162.249.168.129
  • 69.194.242.14
  • 34.11.26.22
  • 72.28.123.107
  • 34.49.192.216
  • 68.67.179.87
  • 72.28.123.104
  • 35.221.60.71
  • 3.167.56.14
  • 3.167.112.93
  • 35.244.154.8
  • 72.28.123.101
  • 172.64.146.215

Autonomous systems (ASN)

  • 14618
  • 26548
  • 26120
  • 396982
  • 36086
  • 29990
  • 16509
  • 13335
  • 15169
  • 14777

Server countries

  • US
  • FR

Linked domains

  • whos.amung.us

Document hash

ede6a0f8ee51c7669c67f66a52419f72f2e52117990e3fad2b55838370f8e2fa

JavaScript globals

  • validateForm
  • $
  • jQuery
  • showlog
  • jQuery11110852611604195213
  • _wau
  • wau_w_col
  • wau_w_siz
  • WAU_ren
  • WAU_dynamic
  • WAU_dynamic_request
  • WAU_r_d
  • WAU_insert
  • WAU_la
  • WAU_addCommas
  • WAU_lrd
  • WAU_lrs
  • WAU_cps
  • docReady
  • x
  • x1
  • x2
  • a
  • cv
  • Tynt
  • _dtspv
  • UAParser
  • _33Across
  • __uspapi
  • lotame_3825
  • char
  • lotameIsCompatible
  • lt3825_ba
  • lt3825_b
  • lt3825_ea
  • lt3825_e
  • lt3825_f
  • lt3825_ga
  • lt3825_ja
  • lt3825_

Cookies

  • df
  • l
  • __cf_bm
  • __dtsu
  • uid
  • cookie
  • done_redirects147
  • pids
  • TapAd_TS
  • TapAd_DID
  • TDID
  • suid
  • mako_uid
  • 33x_ps
  • li_sugr
  • bcookie
  • lidc
  • TapAd_3WAY_SYNCS
  • done_redirects252
  • SERVERID

Browser storage keys

  • _dtspv
  • mm
  • _dtslplu
  • __storage_test__
  • _pubcid
  • _cc_id
  • _cc_cc
  • _cc_aud
  • panoramaId_expiry

TLS session and certificate

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

Domain age, days

5

Registered domain age, days

5

Certificate age, days

54

Certificate validity, days

89

Page requests

38

Provider verdicts

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

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1664d-ed87-75bc-b8ae-5d3018d53627
Final url
https://materimelos04545040.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://materimelos04545040.vercel.app/",
        "from": "http://materimelos04545040.vercel.app/",
        "status": 307
    }
]
Ip
64.29.17.3
Contacted domains
[
    "ps.eyeota.net",
    "cm.g.doubleclick.net",
    "ups.analytics.yahoo.com",
    "match.adsrvr.org",
    "pixel.onaudience.com",
    "tags.crwdcntrl.net",
    "t.dtscout.com",
    "bcp.crwdcntrl.net",
    "i.simpli.fi",
    "d.agkn.com",
    "aa.agkn.com",
    "px.ads.linkedin.com",
    "maxcdn.bootstrapcdn.com",
    "i.postimg.cc",
    "d.turn.com",
    "um.simpli.fi",
    "ssc-cms.33across.com",
    "px.mountain.com",
    "secure.adnxs.com",
    "dp1.33across.com",
    "idsync.rlcdn.com",
    "dp2.33across.com",
    "de.tynt.com",
    "ib.adnxs.com",
    "target.digitalaudience.io",
    "cms.analytics.yahoo.com",
    "t.dtscdn.com",
    "ic.tynt.com",
    "p.mrktmtrcs.net",
    "cdn.tynt.com"
]
Contacted IP addresses
[
    "52.22.182.118",
    "184.194.37.13",
    "162.249.168.129",
    "69.194.242.14",
    "34.11.26.22",
    "72.28.123.107",
    "34.49.192.216",
    "68.67.179.87",
    "72.28.123.104",
    "35.221.60.71",
    "3.167.56.14",
    "3.167.112.93",
    "35.244.154.8",
    "72.28.123.101",
    "172.64.146.215"
]
Asns
[
    "14618",
    "26548",
    "26120",
    "396982",
    "36086",
    "29990",
    "16509",
    "13335",
    "15169",
    "14777"
]
Countries
[
    "US",
    "FR"
]
Linked domains
[
    "whos.amung.us"
]
Document hash
ede6a0f8ee51c7669c67f66a52419f72f2e52117990e3fad2b55838370f8e2fa
Globals
[
    "validateForm",
    "$",
    "jQuery",
    "showlog",
    "jQuery11110852611604195213",
    "_wau",
    "wau_w_col",
    "wau_w_siz",
    "WAU_ren",
    "WAU_dynamic",
    "WAU_dynamic_request",
    "WAU_r_d",
    "WAU_insert",
    "WAU_la",
    "WAU_addCommas",
    "WAU_lrd",
    "WAU_lrs",
    "WAU_cps",
    "docReady",
    "x",
    "x1",
    "x2",
    "a",
    "cv",
    "Tynt",
    "_dtspv",
    "UAParser",
    "_33Across",
    "__uspapi",
    "lotame_3825",
    "char",
    "lotameIsCompatible",
    "lt3825_ba",
    "lt3825_b",
    "lt3825_ea",
    "lt3825_e",
    "lt3825_f",
    "lt3825_ga",
    "lt3825_ja",
    "lt3825_"
]
Cookies
[
    "df",
    "l",
    "__cf_bm",
    "__dtsu",
    "uid",
    "cookie",
    "done_redirects147",
    "pids",
    "TapAd_TS",
    "TapAd_DID",
    "TDID",
    "suid",
    "mako_uid",
    "33x_ps",
    "li_sugr",
    "bcookie",
    "lidc",
    "TapAd_3WAY_SYNCS",
    "done_redirects252",
    "SERVERID"
]
Storage keys
[
    "_dtspv",
    "mm",
    "_dtslplu",
    "__storage_test__",
    "_pubcid",
    "_cc_id",
    "_cc_cc",
    "_cc_aud",
    "panoramaId_expiry"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Domain age days
5
Apex age days
5
Tls age days
54
Tls valid days
89
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
Separate monitor record · 2026-10-23 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1664d-ed87-75bc-b8ae-5d3018d53627
score
0
malicious
false
result_at
2026-10-23T03:30:20Z
enriched_at
2026-10-23T08:16:05Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:20","urlscan_enriched_at":"2026-10-23 10:16:05"}
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

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-23T02:20:34Z

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
10
analyzed_at
2026-10-23T02:20:34Z
source_timestamp
2026-10-23 04:20:34
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: 20 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • letsencrypt.org
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
L1staa de foo7oscatalog0 de nenittass
Open Graph image
https://i.postimg.cc/9MWMPzyz/Whats-App-Image-2024-07-13-at-11-40-05-PM.jpg
Open Graph description
encuentr0, fotoossss

Forms and mixed content

Scripts without SRI
  • https://code.jquery.com/jquery.js
  • https://waust.at/d.js
Third-party scripts
3

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
60
TLS
19
Waiting
17
Connection
6
Download
0
Response time, ms
102

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
6976
CO₂, grams
0.0003
Cleaner than, %
80

DNS servers

Nameservers
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
DNS zone
vercel.app

Location

IP address
216.198.79.67
ASN
16509
Organization
Amazon.com, Inc.
City
Los Angeles
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 64.29.17.67
  • 216.198.79.67

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

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; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
216.198.79.67
IP version
4

Redirects

Redirect chain
  • https://materimelos04545040.vercel.app

Page links

Internal links
1

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "letsencrypt.org",
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "L1staa de foo7oscatalog0 de nenittass",
    "ogImage": "https://i.postimg.cc/9MWMPzyz/Whats-App-Image-2024-07-13-at-11-40-05-PM.jpg",
    "ogDescription": "encuentr0, fotoossss"
}
Forms and mixed content
{
    "no_sri": [
        "https://code.jquery.com/jquery.js",
        "https://waust.at/d.js"
    ],
    "third_party_scripts": 3
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 60,
        "tls": 19,
        "wait": 17,
        "connect": 6,
        "download": 0
    },
    "response_ms": 102
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 6976,
    "co2_grams": 0.0003,
    "cleaner_than": 80
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "216.198.79.67",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Los Angeles",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "64.29.17.67",
        "216.198.79.67"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.198.79.67",
    "family": 4
}
Redirects
{
    "chain": [
        "https://materimelos04545040.vercel.app"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}
Blocklist matchesPhishDestroy · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Last checked

Stored Capture · 9 captures

All capture links and hashes (9)
materimelos04545040.vercel.app: caution — 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card materimelos04545040.vercel.app: caution — 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 2fd90791c06f

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Context United States216.198.79.67 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 10/1001 brand signal
Submitted URLhttp://materimelos04545040.vercel.app/
Favicon Hash
Observed page title
L1staa de foo7os
Automated brand references
Facebook
TLS Certificate
Issued by WR1 · stored validity ends in 27 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States216.198.79.67
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
CYPRESS COMMUNICATIONS, LLC
Observed location
United StatesCleveland, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.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 11:12:41 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 11:12:41 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:12:41 UTC last content: 2026-10-31 11:12:41 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed
DNS8
Ermes
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
MalwareURL
Netcraft
SOCRadar
Sophos
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
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: 38 SHA-256 hashes: 37 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 02:00 UTC.

Open this scan on URLScan 01a1664d-ed87-75bc-b8ae-5d3018d53627 ↗

Stored observation history2

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

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations34

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_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-31 12:12:41.000000
    Evidence SHA-256
    9c5f4a251fa26fb4e0cc37a54e0fae0d14c093f57da8f26c9d1e26a6a5f15596
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:12:41
    Evidence reason
    alive_content
  2. 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-31 12:12:41.000000
    Evidence SHA-256
    9c5f4a251fa26fb4e0cc37a54e0fae0d14c093f57da8f26c9d1e26a6a5f15596
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:12:41
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-31 03:33:49.000000
    Evidence SHA-256
    1a73291a48d42274fe5f6e17cc118335b14816e701e819e5ccd5d555c75c2675
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:33:49
    Evidence reason
    alive_content
  4. 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-31 03:33:49.000000
    Evidence SHA-256
    1a73291a48d42274fe5f6e17cc118335b14816e701e819e5ccd5d555c75c2675
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:33:49
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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:10:34.000000
    Evidence SHA-256
    bf5eec4f28bb7e8fc813eb38fe6dd007e959cec97233f4816225c365dcb475bf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:10:34
    Evidence reason
    alive_content
  6. 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:10:34.000000
    Evidence SHA-256
    bf5eec4f28bb7e8fc813eb38fe6dd007e959cec97233f4816225c365dcb475bf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:10:34
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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:10:38.000000
    Evidence SHA-256
    53bbd69b2f7a10217afd939defc09cb03220bad459898c99e0e158a8a0d8cca0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:10:38
    Evidence reason
    alive_content
  8. 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:10:38.000000
    Evidence SHA-256
    53bbd69b2f7a10217afd939defc09cb03220bad459898c99e0e158a8a0d8cca0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:10:38
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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:11:10.000000
    Evidence SHA-256
    fb5e1bf727c7200bbacece8e7e65f7379af34391ed08e3baaf480b1706009c3d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:11:10
    Evidence reason
    alive_content
  10. 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:11:10.000000
    Evidence SHA-256
    fb5e1bf727c7200bbacece8e7e65f7379af34391ed08e3baaf480b1706009c3d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:11:10
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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 03:39:49.000000
    Evidence SHA-256
    c72077a1769e7bc5f76128b7d5d7f66180939bfc6a260015ff6cd9e5d0361836
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:39:49
    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-29 03:39:49.000000
    Evidence SHA-256
    c72077a1769e7bc5f76128b7d5d7f66180939bfc6a260015ff6cd9e5d0361836
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:39:49
    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
    stale
    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-28 12:06:16.000000
    Evidence SHA-256
    3834eefe1bedd593fca8398e2c844c2ded25af0cfca8322a1851d1b5d1ee7c29
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:06:16
    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-28 12:06:16.000000
    Evidence SHA-256
    3834eefe1bedd593fca8398e2c844c2ded25af0cfca8322a1851d1b5d1ee7c29
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:06:16
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-28 00:06:44.000000
    Evidence SHA-256
    ec49497c11b8cc4f8fc642c1315d8ff0c05a352b553a116218647d73c9b9feef
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:06:44
    Evidence reason
    alive_content
  16. 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-28 00:06:44.000000
    Evidence SHA-256
    ec49497c11b8cc4f8fc642c1315d8ff0c05a352b553a116218647d73c9b9feef
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:06:44
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-27 12:06:34.000000
    Evidence SHA-256
    e186840a6d440654edff1c528fbde29ff87508827acc9fccf4bdf21cc2c650fc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:06:34
    Evidence reason
    alive_content
  18. 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-27 12:06:34.000000
    Evidence SHA-256
    e186840a6d440654edff1c528fbde29ff87508827acc9fccf4bdf21cc2c650fc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:06:34
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-26 12:01:40.000000
    Evidence SHA-256
    b716787ff7dda635e3a022253c41731b423e7012f51279cf5e15929be7a43133
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:40
    Evidence reason
    alive_content
  20. 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-26 12:01:40.000000
    Evidence SHA-256
    b716787ff7dda635e3a022253c41731b423e7012f51279cf5e15929be7a43133
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:40
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-26 00:01:58.000000
    Evidence SHA-256
    6d53d595994271fa2c3f2f086a604eb8fc31027c98664709084bf3440e458794
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:58
    Evidence reason
    alive_content
  22. 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-26 00:01:58.000000
    Evidence SHA-256
    6d53d595994271fa2c3f2f086a604eb8fc31027c98664709084bf3440e458794
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:58
    Evidence reason
    alive_content
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-25 12:02:13.000000
    Evidence SHA-256
    938df6e137f867015a0fab3b4139bcb0c6588120bb452108638e8eb340c3291e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:02:13
    Evidence reason
    alive_content
  24. 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-25 12:02:13.000000
    Evidence SHA-256
    938df6e137f867015a0fab3b4139bcb0c6588120bb452108638e8eb340c3291e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:02:13
    Evidence reason
    alive_content
  25. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-25 03:54:48.000000
    Evidence SHA-256
    bf8ac80d25746ae3dd807c4b2e14a821a9eb1499fb1a453d34086de4d4a2ec87
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:48
    Evidence reason
    alive_content
  26. 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-25 03:54:48.000000
    Evidence SHA-256
    bf8ac80d25746ae3dd807c4b2e14a821a9eb1499fb1a453d34086de4d4a2ec87
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:48
    Evidence reason
    alive_content
  27. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-24 12:00:52.000000
    Evidence SHA-256
    3e4370ad073ede52c2025ef0e440974c3519a70c9be24649c6a96d417c7a83ba
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:52
    Evidence reason
    alive_content
  28. 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-24 12:00:52.000000
    Evidence SHA-256
    3e4370ad073ede52c2025ef0e440974c3519a70c9be24649c6a96d417c7a83ba
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:52
    Evidence reason
    alive_content
  29. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-24 00:01:02.000000
    Evidence SHA-256
    30b46fe07fc7b754dd2fba8492fc86b87bcd5f10c0a699028a729bd4ee01eeee
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:01:02
    Evidence reason
    alive_content
  30. 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-24 00:01:02.000000
    Evidence SHA-256
    30b46fe07fc7b754dd2fba8492fc86b87bcd5f10c0a699028a729bd4ee01eeee
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:01:02
    Evidence reason
    alive_content
  31. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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-23 12:00:54.000000
    Evidence SHA-256
    061e85fd6edd23b737bfacb8d8e77ee6f76eb90cbeeeeee820551b79a51f7b4c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:54
    Evidence reason
    alive_content
  32. 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-23 12:00:54.000000
    Evidence SHA-256
    061e85fd6edd23b737bfacb8d8e77ee6f76eb90cbeeeeee820551b79a51f7b4c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:54
    Evidence reason
    alive_content
  33. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-23 03:10:22.000000
    Evidence SHA-256
    dda21f971d58c79475eff98999ccd462cd553789d31cecb06c3cc6a5ef8eac0f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 03:10:22
    Evidence reason
  34. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-23 03:10:22.000000
    Evidence SHA-256
    dda21f971d58c79475eff98999ccd462cd553789d31cecb06c3cc6a5ef8eac0f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 03:10:22
    Evidence reason

Threat Response Pipeline

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

Recorded events: 9. 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
    materimelos04545040.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 12/92
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, 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

4 entries
  1. Added to PhishDestroy

    materimelos04545040.vercel.app

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    12/92 engine detections

    View source
  4. 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.

Check for cloaking

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

materimelos04545040.vercel.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 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 materimelos04545040.vercel.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/materimelos04545040.vercel.app"
  title="PhishDestroy threat report for materimelos04545040.vercel.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>