Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-10-29T12:09:06Z. Retrieved (as stored): 2026-10-29T19:42:20Z. Listed by external blocklists: PhishFeed. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
scotiaa-jamaica-sd7v.vercel.app favicon

scotiaa-jamaica-sd7v.vercel.app

In short

The captured page at scotiaa-jamaica-sd7v.vercel.app presents a sign-in screen branded with a Scotia wordmark and the heading "Welcome to Scotia OnLine," alongside a Jamaican flag icon. The main interaction is a form asking for a card number or username and a password, followed by a red Sign in button, with a "Forgot your username or password?" link and a remember-me checkbox below the fields.

“Sign in | Scotiabank”

Review the evidence
Registrar
United StatesVercel
Resolved IP
United States64.29.17.67Network Billing Systems · CDN
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
Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
0 / 92
engine detections ·
Google Safe Browsing
Flagged
Blocklist matches
1
PhishFeed
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
7
open gallery
Oct 29, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded scotiaa-jamaica-sd7v.vercel.app on 2026-10-29. Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-10-29T12:09:06Z. Retrieved (as stored): 2026-10-29T19:42:20Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: Vercel. Status: Last known active. Hosting: Network Billing Systems. Listed by external blocklists: PhishFeed. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
1
Hosting
United States64.29.17.67Network Billing Systems · CDN
Registrar
United StatesVercel
Page captures
7
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-29T19:44:16Z
SHA-256: d5f3530986646ccda4c6974306c56bf442a2d3afd6d7178f51140bca137d8b3d

PhishDestroy analysis, reviewed version

The captured page at scotiaa-jamaica-sd7v.vercel.app presents a sign-in screen branded with a Scotia wordmark and the heading "Welcome to Scotia OnLine," alongside a Jamaican flag icon. The main interaction is a form asking for a card number or username and a password, followed by a red Sign in button, with a "Forgot your username or password?" link and a remember-me checkbox below the fields.

PhishDestroy's VirusTotal check for this domain returned 0 detections out of 92 engines, with 0 malicious and 0 suspicious verdicts, retrieved on 2026-10-29. No vendor verdicts were flagged in that result, so no representative vendors can be named from this scan.

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

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

a7d5e10c-b3a9-4788-9f0b-ec9a78967bb6

Final URL

https://scotiaa-jamaica-sd7v.vercel.app/

HTTP response

200

Navigation history

  • URL
    https://scotiaa-jamaica-sd7v.vercel.app/
    Status
    200

DOM structure hash

17ec79938cd623f446199481476afa57f768409b234a4f815d3a765232975c46

Document hash

bdffb2de9fdbac2453d8fa2c55d34ff70a16b73757dd7e5f7c7f261ee72a4f64

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    scotiaa-jamaica-sd7v.vercel.app
    Type
    A
    Value
    64.29.17.195
  • Name
    scotiaa-jamaica-sd7v.vercel.app
    Type
    A
    Value
    216.198.79.195

DNSSEC valid

No

IP address

127.0.1.14

127.0.1.14 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
Tucows Domains Inc
Registered
Updated
Expires
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
Original source fields · JSON
Uuid
a7d5e10c-b3a9-4788-9f0b-ec9a78967bb6
Final url
https://scotiaa-jamaica-sd7v.vercel.app/
Status
200
History
[
    {
        "url": "https://scotiaa-jamaica-sd7v.vercel.app/",
        "status": 200
    }
]
DOM structure hash
17ec79938cd623f446199481476afa57f768409b234a4f815d3a765232975c46
Document hash
bdffb2de9fdbac2453d8fa2c55d34ff70a16b73757dd7e5f7c7f261ee72a4f64
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "scotiaa-jamaica-sd7v.vercel.app",
        "type": "A",
        "value": "64.29.17.195"
    },
    {
        "name": "scotiaa-jamaica-sd7v.vercel.app",
        "type": "A",
        "value": "216.198.79.195"
    }
]
Dnssec valid
false
Ip
127.0.1.14

127.0.1.14 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": "Tucows Domains Inc",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2026-03-14T03:03:04Z",
    "expires": "2036-01-28T03:03:04Z",
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ]
}

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 8ab1be04b94b9e35f2fb593e73efcc5dff513ae00e24c81a0e79954cd1f70ca5

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a187e6-a4ef-75fd-b387-d70de67f34d3

Final URL

https://scotiaa-jamaica-sd7v.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://scotiaa-jamaica-sd7v.vercel.app/
    From
    http://scotiaa-jamaica-sd7v.vercel.app/
    Status
    307

IP address

64.29.17.3

Contacted domains

  • www.googletagmanager.com
  • firebaseinstallations.googleapis.com
  • firebase.googleapis.com

Contacted IP addresses

  • 64.29.17.3

Autonomous systems (ASN)

  • 16509

Server countries

  • US

Document hash

bdffb2de9fdbac2453d8fa2c55d34ff70a16b73757dd7e5f7c7f261ee72a4f64

Script hashes

  • 464db66f91b22db41c7e37d17e8c1fab865c65373dfb06edc1711e286f01a060

JavaScript globals

  • dataLayer
  • gtag

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

0

Registered domain age, days

0

Certificate age, days

60

Certificate validity, days

89

Page requests

15

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • scotiabank
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Scotiabank
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a187e6-a4ef-75fd-b387-d70de67f34d3
Final url
https://scotiaa-jamaica-sd7v.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://scotiaa-jamaica-sd7v.vercel.app/",
        "from": "http://scotiaa-jamaica-sd7v.vercel.app/",
        "status": 307
    }
]
Ip
64.29.17.3
Contacted domains
[
    "www.googletagmanager.com",
    "firebaseinstallations.googleapis.com",
    "firebase.googleapis.com"
]
Contacted IP addresses
[
    "64.29.17.3"
]
Asns
[
    "16509"
]
Countries
[
    "US"
]
Document hash
bdffb2de9fdbac2453d8fa2c55d34ff70a16b73757dd7e5f7c7f261ee72a4f64
Script hashes
[
    "464db66f91b22db41c7e37d17e8c1fab865c65373dfb06edc1711e286f01a060"
]
Globals
[
    "dataLayer",
    "gtag"
]
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
0
Apex age days
0
Tls age days
60
Tls valid days
89
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "scotiabank"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Scotiabank"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
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
01a187e6-a4ef-75fd-b387-d70de67f34d3
score
100
malicious
true
result_at
2026-10-30T04:30:21Z
enriched_at
2026-10-30T09:11:46Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:21","urlscan_enriched_at":"2026-10-30 10:11:46"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
0
Suspicious
0
Undetected
92

Reputation score

0

Tags

  • dga

Categories

Google
financial_services
Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
Forcepoint ThreatSeeker
information technology

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.67
  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.67

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": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Google": "financial_services",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "Forcepoint ThreatSeeker": "information technology"
}
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-29T04:07:32Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.67"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.67"
    }
]
Dns at
2026-10-29T12:09:32Z
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 collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
23
denominator
92
malicious
null
suspicious
null
vendors
["Criminal IP","alphaMountain.ai","BitDefender","CSIS Security Group","Ermes","ESET","Emsisoft","Forcepoint ThreatSeeker","Fortinet","Fortra","G-Data","Google Safe Browsing","Gridinsoft","Kaspersky","LevelBlue","Lionic","MalwareURL","Netcraft","SOCRadar","Sophos","URLQuery","VIPRE","Webroot"]
observed_at
null
checked_at
2026-11-02 04:01:22
fetched_at
2026-11-02 03:01:22
time_basis
as stored; legacy timezone not established

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

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

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:14Z
source_timestamp
2026-10-29 16:20:14
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
scotiaa-jamaica-sd7v.vercel.app — Scotiabank sign-in page capture
ai_description
PhishDestroy records scotiaa-jamaica-sd7v.vercel.app as a captured page presenting a Scotiabank-branded sign-in form for Scotia OnLine.
ai_summary
The captured page at scotiaa-jamaica-sd7v.vercel.app presents a sign-in screen branded with a Scotia wordmark and the heading "Welcome to Scotia OnLine," alongside a Jamaican flag icon. The main interaction is a form asking for a card number or username and a password, followed by a red Sign in button, with a "Forgot your username or password?" link and a remember-me checkbox below the fields. PhishDestroy's VirusTotal check for this domain returned 0 detections out of 92 engines, with 0 malicious and 0 suspicious verdicts, retrieved on 2026-10-29. No vendor verdicts were flagged in that result, so no representative vendors can be named from this scan.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 20:48:20
revision
a40521ec54d0531464d123de6425f082b32be2ce192ca05bcb100d6c15ac5a97
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

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

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
2005

Page title and metadata

Page title
Sign in | Scotiabank

Trackers

Requests
13
Observed services
  • Name
    Google Tag
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    Google Analytics
    Company
    Google
    Country
    US
    Category
    Site Analytics
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
30
TLS
19
Waiting
15
Connection
6
Download
1
Response time, ms
71

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
2798
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

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

Cookies

Cookies
  • Name
    _ga_R4NNS2SPR0
  • Name
    _ga

Location

IP address
216.198.79.3
ASN
16509
Organization
Network Billing Systems
City
Atlanta
Country
US

TLS certificate

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

DNS records

A
  • 216.198.79.3
  • 64.29.17.3

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.3
IP version
4

Redirects

Redirect chain
  • https://scotiaa-jamaica-sd7v.vercel.app

Page links

Internal links
2

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": [
        "pki.goog",
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-29T13:42:29Z",
    "first": "2026-10-29T13:42:29Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2005
}
Page title and metadata
{
    "title": "Sign in | Scotiabank"
}
Trackers
{
    "requests": 13,
    "trackers": [
        {
            "name": "Google Tag",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Analytics",
            "company": "Google",
            "country": "US",
            "category": "Site Analytics",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 30,
        "tls": 19,
        "wait": 15,
        "connect": 6,
        "download": 1
    },
    "response_ms": 71
}
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": 2798,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "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"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Cookies
{
    "cookies": [
        {
            "name": "_ga_R4NNS2SPR0"
        },
        {
            "name": "_ga"
        }
    ]
}
Location
{
    "ip": "216.198.79.3",
    "asn": "16509",
    "org": "Network Billing Systems",
    "city": "Atlanta",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "216.198.79.3",
        "64.29.17.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://scotiaa-jamaica-sd7v.vercel.app"
    ]
}
Page links
{
    "internal_count": 2
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about scotiaa-jamaica-sd7v.vercel.app

Is scotiaa-jamaica-sd7v.vercel.app legit?

PhishDestroy rates scotiaa-jamaica-sd7v.vercel.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-29. Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-10-29T12:09:06Z. Retrieved (as stored): 2026-10-29T19:42:20Z. Google Safe Browsing flags it. Listed by external blocklists: PhishFeed. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is scotiaa-jamaica-sd7v.vercel.app safe to connect a wallet?

This report does not record which wallet requests scotiaa-jamaica-sd7v.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 scotiaa-jamaica-sd7v.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

Blocklist matchesPhishDestroy · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Checked, no match

Last checked

Stored Capture · 7 captures

Cloudflare Radar 1 / 7 Used in the analysis Source file SHA-256: d5f3530986646ccda4c6974306c56bf442a2d3afd6d7178f51140bca137d8b3d SHA-256 of the prepared copy given to the model: 508f7970f9e35d589ab7862e1e907970a83f8a275d69b6cf94bc5c7f1df41d8c
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://scotiaa-jamaica-sd7v.vercel.app/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)
scotiaa-jamaica-sd7v.vercel.app: phishdestroy risk analysis, risk score 65/100 (high); not yet listed by external security vendors.
Social preview card scotiaa-jamaica-sd7v.vercel.app: phishdestroy risk analysis, risk score 65/100 (high); not yet listed by external security vendors. v 50055c80cdf9

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Scotiabank report ↗
Google Safe Browsing Flagged Social engineering checked Nov 7, 2026
IP Context United States64.29.17.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
HTTP Status200
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://scotiaa-jamaica-sd7v.vercel.app/
Favicon Hash
Observed page title
Sign in | Scotiabank
TLS Certificate
Issued by WR1 · stored validity ends in 19 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States64.29.17.67
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Network Billing Systems
Observed location
United StatesAtlanta, 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-11-07 23:16: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-11-07 23:16:41 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 11:15:23 UTC last content: 2026-11-07 11:15:23 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

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of scotiaa-jamaica-sd7v.vercel.app · checked Oct 29, 2026

96
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
2.53 s
Largest Contentful Paint
CLS
0.065
Cumulative Layout Shift
TBT
81 ms
Total Blocking Time
SI
0.76 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://scotiaa-jamaica-sd7v.vercel.app/
Final URL: https://scotiaa-jamaica-sd7v.vercel.app/
Sign in | Scotiabank
Response
HTTP 200
HTML body
2.7 KB
Compressed
1.1 KB
Links
2 internal · 0 external
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 · 14
Access-Control-Allow-Origin
*
Age
39169
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Thu, 29 Oct 2026 13:42:20 GMT
Etag
W/"441a88c6606c8e4efb7eb8dccccb5df6"
Last-Modified
Thu, 29 Oct 2026 02:49:30 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
X-Vercel-Cache
HIT
X-Vercel-Id
fra1::5k2jx-1793281340091-fcf222b95a24

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.

Captured network requests

Network requests: 15 SHA-256 hashes: 8 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:46 UTC.

Open this scan on URLScan 01a187e6-a4ef-75fd-b387-d70de67f34d3 ↗

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations31

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-11-08 00:16:41.000000
    Evidence SHA-256
    e3602e4704b0570502c2bd347e24b68cf7f3880e0873b82141a4d7c4e470c957
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:16:41
    Evidence reason
    alive_content
  2. 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-11-07 12:15:23.000000
    Evidence SHA-256
    3b5efb99dd3e073f1ad17197890dda5081c1e9e0ab39c35c44df6e12e48ab155
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:15:23
    Evidence reason
    alive_content
  3. 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-11-07 12:15:23.000000
    Evidence SHA-256
    3b5efb99dd3e073f1ad17197890dda5081c1e9e0ab39c35c44df6e12e48ab155
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:15:23
    Evidence reason
    alive_content
  4. 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-11-07 03:54:19.000000
    Evidence SHA-256
    df638747fece4aef51b30cbb326f4bf280d51a3f2a465e62b49831f35276e8f0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 03:54:19
    Evidence reason
    alive_content
  5. 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-11-07 03:54:19.000000
    Evidence SHA-256
    df638747fece4aef51b30cbb326f4bf280d51a3f2a465e62b49831f35276e8f0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 03:54:19
    Evidence reason
    alive_content
  6. 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-11-07 00:06:59.000000
    Evidence SHA-256
    404b3e538a6735ecd3ebba51eb0f9dd7721bd113e498548e298c456f9e1f37fa
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:06:59
    Evidence reason
    alive_content
  7. 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-11-07 00:06:59.000000
    Evidence SHA-256
    404b3e538a6735ecd3ebba51eb0f9dd7721bd113e498548e298c456f9e1f37fa
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:06:59
    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-11-05 03:31:39.000000
    Evidence SHA-256
    53080652059dac19c1a8f13f079daf5a4069a3274ac54f24c383cb9f43b1a608
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:31:39
    Evidence reason
    alive_content
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:39.000000
    Evidence SHA-256
    88bb2eb55fcf19dc3fa2dd05c4666a5083bc47b8c7d1129b633e86b9eeb50f25
    Evidence timestamp as recorded
    2026-11-05 03:31:39
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  10. 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-11-04 12:07:48.000000
    Evidence SHA-256
    f130c79dd04f0e97b3fef23a5448bcb0e6f4433ab426facea792584a202e77ca
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:07:48
    Evidence reason
    alive_content
  11. 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-11-04 12:07:48.000000
    Evidence SHA-256
    f130c79dd04f0e97b3fef23a5448bcb0e6f4433ab426facea792584a202e77ca
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:07:48
    Evidence reason
    alive_content
  12. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:01:51.000000
    Evidence SHA-256
    387e69843c1174dccfd024f962b1b5227fe579a9fc8bd9ec6b70dafddabfdcab
    Evidence timestamp as recorded
    2026-11-02 12:01:51
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  13. 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-11-02 12:01:51.000000
    Evidence SHA-256
    a7158825b5ed99a786430cbc362da348a17fd8af34a78b3966241bf237ab4364
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:01:51
    Evidence reason
    alive_content
  14. 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-11-02 00:04:35.000000
    Evidence SHA-256
    6467f1b29acd303e8f72ff13dfb13c2db6dc68de00d007a8d841efc640689e6e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:04:35
    Evidence reason
    alive_content
  15. 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-11-02 00:04:35.000000
    Evidence SHA-256
    6467f1b29acd303e8f72ff13dfb13c2db6dc68de00d007a8d841efc640689e6e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:04:35
    Evidence reason
    alive_content
  16. 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-11-01 12:05:23.000000
    Evidence SHA-256
    6e52b3eb78b7d37117a3225a33b11a6186efe2a88410db2e01e9742b2574b616
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:05:23
    Evidence reason
    alive_content
  17. 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-11-01 12:05:23.000000
    Evidence SHA-256
    6e52b3eb78b7d37117a3225a33b11a6186efe2a88410db2e01e9742b2574b616
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:05:23
    Evidence reason
    alive_content
  18. 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-11-01 03:48:50.000000
    Evidence SHA-256
    be4acbacf7a04297d9cc523ee796af04ec40284240ec013c7cc2b9c873e28df2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:48:50
    Evidence reason
    alive_content
  19. 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-11-01 03:48:50.000000
    Evidence SHA-256
    be4acbacf7a04297d9cc523ee796af04ec40284240ec013c7cc2b9c873e28df2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:48:50
    Evidence reason
    alive_content
  20. 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-11-01 00:03:48.000000
    Evidence SHA-256
    7e36db2ee46362f9901d2be166b8ebb8bb551ebad8bb1b4f98995e55beb4eb9d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:03:48
    Evidence reason
    alive_content
  21. 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-11-01 00:03:48.000000
    Evidence SHA-256
    7e36db2ee46362f9901d2be166b8ebb8bb551ebad8bb1b4f98995e55beb4eb9d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:03:48
    Evidence reason
    alive_content
  22. 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:04:11.000000
    Evidence SHA-256
    a6803c63377822d07264158cc5fa85a8503b1eae6339f81d6534c9625adcf835
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:11
    Evidence reason
    alive_content
  23. 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:04:11.000000
    Evidence SHA-256
    a6803c63377822d07264158cc5fa85a8503b1eae6339f81d6534c9625adcf835
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:11
    Evidence reason
    alive_content
  24. 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 00:57:58.000000
    Evidence SHA-256
    b85f0d7dc179da4ca129ddec4f42083e221e909ca075c9ca32ee0b99c95c42bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:57:58
    Evidence reason
    alive_content
  25. 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 00:57:58.000000
    Evidence SHA-256
    b85f0d7dc179da4ca129ddec4f42083e221e909ca075c9ca32ee0b99c95c42bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:57:58
    Evidence reason
    alive_content
  26. 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 13:10:22.000000
    Evidence SHA-256
    9dd5b9ebc1d396175ca1a18605b3eca4c4ce05a29df60046355d0bbf4a7e48b3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:22
    Evidence reason
    alive_content
  27. 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 13:10:22.000000
    Evidence SHA-256
    9dd5b9ebc1d396175ca1a18605b3eca4c4ce05a29df60046355d0bbf4a7e48b3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:22
    Evidence reason
    alive_content
  28. 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 01:23:27.000000
    Evidence SHA-256
    5ef3b251c99452c041eebbeb74d3b11309dc0df6da0c1e5e0265e3f7ffdbc0ae
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:27
    Evidence reason
    alive_content
  29. 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 01:23:27.000000
    Evidence SHA-256
    5ef3b251c99452c041eebbeb74d3b11309dc0df6da0c1e5e0265e3f7ffdbc0ae
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:27
    Evidence reason
    alive_content
  30. 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:45:23.000000
    Evidence SHA-256
    e1fbbc37119817d7b666ce2e53e6cbf7fd5b1eca308b6c1d2111e175a3abc20d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 14:45:23
    Evidence reason
  31. 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:45:23.000000
    Evidence SHA-256
    e1fbbc37119817d7b666ce2e53e6cbf7fd5b1eca308b6c1d2111e175a3abc20d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 14:45:23
    Evidence reason

Threat Response Pipeline

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

Recorded events: 12. 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
    scotiaa-jamaica-sd7v.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Google Safe Browsing · Blocklist Detection · Cloudflare Radar: Malicious · Automated brand label: Scotiabank · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • 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
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Phishing, Security threats
  • Automated brand label: Scotiabank
    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. Added to PhishDestroy

    scotiaa-jamaica-sd7v.vercel.app

    View source
  4. URLScan

    Page captured

    View source
  5. Wayback Machine

    Page archived

    View source
  6. VirusTotal

    0/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

scotiaa-jamaica-sd7v.vercel.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid 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?

2 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 scotiaa-jamaica-sd7v.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

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/scotiaa-jamaica-sd7v.vercel.app"
  title="PhishDestroy threat report for scotiaa-jamaica-sd7v.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>