Skip to security report
Analytics Dashboard
Domain security and threat intelligence
challenge-3-react.vercel.app favicon

challenge-3-react.vercel.app

In short

challenge-3-react.vercel.app is a phishing page detected by PhishDestroy on 2026-10-24.

“Porto Seguro”

Review the evidence
Registrar
Vercel
Resolved IP
64.29.17.67
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Record details & risk signals
Oct 24, 2026 CDN
Risk signals
VirusTotal detections: 13/92
VirusTotal
13 / 92
engine detections
Page captures
5
open gallery
API
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Critical
  • VirusTotal detections: 13/92
  • Last known active
Source counts
VirusTotal
13 / 92
Page captures
5
Domain summary

challenge-3-react.vercel.app is a phishing page detected by PhishDestroy on 2026-10-24. Risk: critical (99/100). Registrar: Vercel. Status: Last known active. Hosting: Amazon.com, Inc. VirusTotal: 13/92 engines flag it. Do not enter credentials or connect a wallet.

Page captures Source results Registration record

PhishDestroy threat report

challenge-3-react.vercel.app is a tenant hostname on Vercel, not a separately registered domain. PhishDestroy first observed the hostname on Oct 24, 2026. The captured page title is “Porto Seguro”. Current evidence score: 99/100 (critical).

One source contains a positive finding: VirusTotal. VirusTotal recorded 13 detections among 92 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Lionic, SOCRadar, Sophos, VIPRE, Webroot on Oct 14, 2026 at 23:47 UTC.

HTTP 200 was recorded on Oct 24, 2026 at 23:06 UTC. Latest classified outcome: live content observed; cause content served on Oct 24, 2026 at 09:13 UTC. Vercel is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 64.29.17.67 on AS16509 (Amazon.com, Inc.). The IP and ASN identify shared Vercel infrastructure, not the tenant operator. DOM analysis on Oct 24, 2026 at 10:20 UTC returned 93/100. The evidence archive retains 5 visual captures from PhishDestroy and URLScan. The platform TLS certificate was issued by WR1 with validity through Nov 27, 2026.

Stored content provides classification context alongside the positive source finding.

Source evidenceVirusTotal 13 / 92 4 sources
SourceResultRecorded · UTCEvidence

VirusTotal

13 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Questions about challenge-3-react.vercel.app

Is challenge-3-react.vercel.app legit?

No. PhishDestroy classifies challenge-3-react.vercel.app as a phishing page (risk: critical, 99/100); it was first detected on 2026-10-24. VirusTotal: 13/92 engines flag it. Treat the site as unsafe.

Is challenge-3-react.vercel.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on challenge-3-react.vercel.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used challenge-3-react.vercel.app?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-10-24 08:06 UTC
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 5
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 93/100
Submitted URLhttp://challenge-3-react.vercel.app/
Observed page title
Porto Seguro
TLS Certificate
Issued by WR1 · stored validity ends in 33 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.29.17.67
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Walnut, 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.

viewdns.info · 64.29.17.67rapiddns.io

Latest Classified Outcome 2026-10-24 11:13:45 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-24 11:13:45 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-24 11:13:45 UTC last content: 2026-10-24 11:13:45 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

13 / 92 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
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://challenge-3-react.vercel.app/
Final URL: https://challenge-3-react.vercel.app/
Porto Seguro
Response
HTTP 200
HTML body
23.3 KB
Compressed
3.9 KB
Links
29 internal · 1 external
Detected technologies
react
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 15
Access-Control-Allow-Origin
*
Age
991908
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 24 Oct 2026 08:03:57 GMT
Etag
W/"7894ba3f29d2167b80cb91187d9c312c"
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Url
X-Matched-Path
/
X-Vercel-Cache
HIT
X-Vercel-Id
fra1::kd65r-1792829037974-d9cfeb6462ff

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

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

Collected source details

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

Every stored field, with its source and date
URLScan · 2026-10-24T08:04:47Z

Observed: · Retrieved:

Uuid
01a16cf0-c2d3-713d-a423-e304e24a1d9b
Final url
https://challenge-3-react.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://challenge-3-react.vercel.app/",
        "from": "http://challenge-3-react.vercel.app/",
        "status": 307
    }
]
Ip
216.198.79.3
Contacted domains
[
    "fonts.googleapis.com",
    "fonts.gstatic.com"
]
Contacted IP addresses
[
    "142.250.195.227",
    "142.250.183.42",
    "216.198.79.3"
]
Asns
[
    "15169",
    "16509"
]
Countries
[
    "US"
]
Linked domains
[
    "github.com"
]
Social
[
    "https://github.com/MaatheusOM1/Challenge-3-React"
]
Document hash
ca50ea1e9612163acb05599d783191c4d2f85b321b2ebf0fefa2063f76cbab16
Script hashes
[
    "b62fafe105f2f8407eecbf09b4d05c14a7456dc11e80667e80c40478edef795c",
    "ecf5645d5ec8f5acdc5c9667b5ec19a789d4faea07ed79f7eeee6bddec25aa8e",
    "1d293701c6628dfb0dcebc368b83d8a79316dd8c3874aec6c06e6701d1bc503a",
    "f75a545a28209d8680a4c7aee99a6b7e3ee1a0226cd3b09bef9748f9e37a46ad"
]
Globals
[
    "webpackChunk_N_E",
    "__next_f",
    "next",
    "__next_require__",
    "__next_chunk_load__"
]
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
238
Apex age days
2461
Tls age days
55
Tls valid days
89
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "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"
}
VirusTotal · 2026-10-14T23:47:45Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 13,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
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-02-27T15:45:42Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.195"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.195"
    }
]
Dns at
2026-10-14T23:47:57Z
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"
}
Website checks · 2026-10-24T09:28:30Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "pki.goog",
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-24T09:05:15Z",
    "first": "2026-10-24T09:05:15Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 5032
}
Page title and metadata
{
    "title": "Porto Seguro"
}
Trackers
{
    "requests": 19,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 34,
        "tls": 11,
        "wait": 34,
        "connect": 7,
        "download": 0
    },
    "response_ms": 86
}
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": 23871,
    "co2_grams": 0.0009,
    "cleaner_than": 53
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        },
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "216.198.79.3",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "64.29.17.3",
        "216.198.79.3"
    ]
}
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.3",
    "family": 4
}
Redirects
{
    "chain": [
        "https://challenge-3-react.vercel.app"
    ]
}
Page links
{
    "external": [
        "https://github.com/MaatheusOM1/Challenge-3-React"
    ],
    "external_count": 1,
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}
Stored observation history3

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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  3. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. VirusTotal

    13/92 engine detections

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    challenge-3-react.vercel.app

    View source
  4. URLScan

    Page captured

    View source

Check for cloaking

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

challenge-3-react.vercel.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 13 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid 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
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including challenge-3-react.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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

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/challenge-3-react.vercel.app"
  title="PhishDestroy threat report for challenge-3-react.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>