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

jpmorganpurchase.web.app

In short

PhishDestroy records the reCAPTCHA verification page captured at jpmorganpurchase.web.app, showing an IP address and a Google search URL.

“https://www.google.com/search?q=covid&sei=krzjauKhG-urxc8P7qGc8Qg”

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
United States199.36.158.100Fastly, Inc. · CDN
First observed
Oct 29, 2026
PhishDestroy assessment Critical
96/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 12/92
VirusTotal
12 / 92
engine detections ·
Page captures
3
open gallery
Oct 29, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records the reCAPTCHA verification page captured at jpmorganpurchase.web.app, showing an IP address and a Google search URL.

Critical
Status
Last known active
VirusTotal
12 / 92
Hosting
United States199.36.158.100Fastly, Inc. · CDN
Registrar
United StatesGoogle Domains
Page captures
3
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at jpmorganpurchase.web.app presents a reCAPTCHA challenge asking the visitor to confirm they are not a robot. Below the checkbox, Ukrainian text explains that unusual traffic was detected from the visitor's computer network and that the page checks whether requests come from a person rather than a bot. The page also displays an IP address, a timestamp, and a URL pointing to a Google search query about covid.

The stored VirusTotal domain result reports 12 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".

Source evidenceVirusTotal 12 / 92 8 sources

VirusTotal

12 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
12
Suspicious
0
Undetected
31

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Fortinet
phishing
Kaspersky
phishing
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    A
    Value
    199.36.158.100
  • TTL, seconds
    21600
    Type
    AAAA
    Value
    2620:0:890::100

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • web.app
  • *.web.app
Issuer
Google Trust Services / WR4
Serial
e26d762a101120cd12a8f68d86c31d05
SHA-256
7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Subject
web.app
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.googledomains.com
  • ns2.googledomains.com
  • ns3.googledomains.com
  • ns4.googledomains.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2019-01-08T22:05:04Z
Expires
2026-01-08T22:05:04Z
Updated
2024-12-12T10:14:49Z
First seen
2023-09-28T19:45:05Z
DNS records
[
    {
        "ttl": 21600,
        "type": "A",
        "value": "199.36.158.100"
    },
    {
        "ttl": 21600,
        "type": "AAAA",
        "value": "2620:0:890::100"
    }
]
Dns at
2026-10-17T13:01:27Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "issuer": "Google Trust Services / WR4",
    "serial": "e26d762a101120cd12a8f68d86c31d05",
    "sha256": "7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095",
    "subject": "web.app",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2019-01-08T22:05:04Z",
    "updated": "2024-12-12T10:14:49Z",
    "expires": "2026-01-08T22:05:04Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.googledomains.com",
        "ns2.googledomains.com",
        "ns3.googledomains.com",
        "ns4.googledomains.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 12 malicious + 0 suspicious / 92 · 2026-10-17 12:56:22 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-17T12:56:22Z
fetched_at
2026-10-29T21:40:43Z
stats
{"timeout":0,"harmless":49,"malicious":12,"suspicious":0,"undetected":31}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

205b8375-e0d4-4b8e-9d3d-1a9778778eca

Final URL

https://www.google.com/sorry/index

HTTP response

429

Navigation history

  • URL
    https://jpmorganpurchase.web.app/
    Status
    200
  • URL
    https://www.google.com/search
    Status
    200
  • URL
    https://www.google.com/search
    Status
    302
  • URL
    https://www.google.com/sorry/index
    Status
    429

DOM structure hash

351149e9c24a430a2f7798d996fb27278fbd3c0e13b716b34f98c2374ef237c6

Document hash

7b610148780551ee010ee8d0b0db41551ad2438d079c8399f1a49eb62065aff2

Domain risk categories

  • Search Engines
  • Technology
  • News, Portal & Search

Cloudflare Radar rank

Rank
1
Rank range
200

DNS records

  • Name
    www.google.com
    Type
    A
    Value
    142.251.156.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.152.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.153.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.150.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.154.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.155.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.157.119
  • Name
    www.google.com
    Type
    A
    Value
    142.251.151.119
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:482a:7700::
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:4827:7700::
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:4826:7700::
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:482c:7700::
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:4829:7700::
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:482b:7700::
  • Name
    www.google.com
    Type
    AAAA
    Value
    2001:4860:4828:7700::

DNSSEC valid

No

IP address

127.0.1.22

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

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com
Original source fields · JSON
Uuid
205b8375-e0d4-4b8e-9d3d-1a9778778eca
Final url
https://www.google.com/sorry/index
Status
429
History
[
    {
        "url": "https://jpmorganpurchase.web.app/",
        "status": 200
    },
    {
        "url": "https://www.google.com/search",
        "status": 200
    },
    {
        "url": "https://www.google.com/search",
        "status": 302
    },
    {
        "url": "https://www.google.com/sorry/index",
        "status": 429
    }
]
DOM structure hash
351149e9c24a430a2f7798d996fb27278fbd3c0e13b716b34f98c2374ef237c6
Document hash
7b610148780551ee010ee8d0b0db41551ad2438d079c8399f1a49eb62065aff2
Domain risks
[
    "Search Engines",
    "Technology",
    "News, Portal & Search"
]
Radar rank
{
    "rank": 1,
    "bucket": "200"
}
DNS records
[
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.156.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.152.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.153.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.150.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.154.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.155.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.157.119"
    },
    {
        "name": "www.google.com",
        "type": "A",
        "value": "142.251.151.119"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:482a:7700::"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:4827:7700::"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:4826:7700::"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:482c:7700::"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:4829:7700::"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:482b:7700::"
    },
    {
        "name": "www.google.com",
        "type": "AAAA",
        "value": "2001:4860:4828:7700::"
    }
]
Dnssec valid
false
Ip
127.0.1.22

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

Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "1997-09-15T04:00:00Z",
    "updated": "2019-09-09T15:39:04Z",
    "expires": "2028-09-14T04:00:00Z",
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 74000d2139b0d05e4a68c971b2b9e89e8ca9bd8f45963a4917d67ff742785e8a

Open report
URLScanOriginal source recordObserved: 25 fields

Observed: · Retrieved:

Report ID

01a18998-98d9-7208-9c9e-c4e902b3a922

Final URL

https://www.google.com/sorry/index

HTTP response

429

Redirect type

off-domain

Redirects

  • To
    https://jpmorganpurchase.web.app/
    From
    http://jpmorganpurchase.web.app/
    Status
    307
  • To
    https://www.google.com/search
    From
    https://jpmorganpurchase.web.app/
  • To
    https://www.google.com/search
    From
    https://www.google.com/search
  • To
    https://www.google.com/sorry/index
    From
    https://www.google.com/search
    Status
    302

IP address

142.251.155.119

Contacted domains

  • www.gstatic.com
  • fonts.gstatic.com
  • jpmorganpurchase.web.app
  • api.telegram.org

Contacted IP addresses

  • 142.250.154.94
  • 2001:4860:482a:7800::
  • 142.251.155.119
  • 2001:67c:4e8:f004::9
  • 2620:0:890::100

Autonomous systems (ASN)

  • 15169
  • 62041
  • 54113

Server countries

  • US
  • NL

Linked domains

  • support.google.com

Document hash

7b610148780551ee010ee8d0b0db41551ad2438d079c8399f1a49eb62065aff2

Script hashes

  • 504021dc6f945ae3c00c52a81b5795d9461c7b382349c6ba7ca9651c5f42c887

JavaScript globals

  • submitCallback
  • ___grecaptcha_cfg
  • grecaptcha
  • __recaptcha_api
  • __google_recaptcha_client
  • closure_lm_71718
  • scrypt
  • e

Cookies

  • SEARCH_SAMESITE
  • AEC
  • __Secure-ENID

Browser storage keys

  • krzjauKhG-urxc8P7qGc8Qg
  • rc::a
  • rc::c

TLS session and certificate

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

Domain age, days

4965

Registered domain age, days

4965

Certificate age, days

22

Certificate validity, days

83

Cisco Umbrella rank

7

Page requests

20

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Uuid
01a18998-98d9-7208-9c9e-c4e902b3a922
Final url
https://www.google.com/sorry/index
Status
429
Redirected
off-domain
Redirects
[
    {
        "to": "https://jpmorganpurchase.web.app/",
        "from": "http://jpmorganpurchase.web.app/",
        "status": 307
    },
    {
        "to": "https://www.google.com/search",
        "from": "https://jpmorganpurchase.web.app/"
    },
    {
        "to": "https://www.google.com/search",
        "from": "https://www.google.com/search"
    },
    {
        "to": "https://www.google.com/sorry/index",
        "from": "https://www.google.com/search",
        "status": 302
    }
]
Ip
142.251.155.119
Contacted domains
[
    "www.gstatic.com",
    "fonts.gstatic.com",
    "jpmorganpurchase.web.app",
    "api.telegram.org"
]
Contacted IP addresses
[
    "142.250.154.94",
    "2001:4860:482a:7800::",
    "142.251.155.119",
    "2001:67c:4e8:f004::9",
    "2620:0:890::100"
]
Asns
[
    "15169",
    "62041",
    "54113"
]
Countries
[
    "US",
    "NL"
]
Linked domains
[
    "support.google.com"
]
Document hash
7b610148780551ee010ee8d0b0db41551ad2438d079c8399f1a49eb62065aff2
Script hashes
[
    "504021dc6f945ae3c00c52a81b5795d9461c7b382349c6ba7ca9651c5f42c887"
]
Globals
[
    "submitCallback",
    "___grecaptcha_cfg",
    "grecaptcha",
    "__recaptcha_api",
    "__google_recaptcha_client",
    "closure_lm_71718",
    "scrypt",
    "e"
]
Cookies
[
    "SEARCH_SAMESITE",
    "AEC",
    "__Secure-ENID"
]
Storage keys
[
    "krzjauKhG-urxc8P7qGc8Qg",
    "rc::a",
    "rc::c"
]
Tls
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR3",
    "subject": "web.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T22:53:04Z",
    "valid_from": "2026-10-27T22:53:05Z"
}
Domain age days
4965
Apex age days
4965
Tls age days
22
Tls valid days
83
Umbrella rank
7
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -96,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556926; 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
01a18998-98d9-7208-9c9e-c4e902b3a922
score
0
malicious
false
result_at
2026-10-30T04:30:15Z
enriched_at
2026-10-30T09:10:50Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:15","urlscan_enriched_at":"2026-10-30 10:10:50"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-29T21:55:09Z

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-29T21:55:09Z
source_timestamp
2026-10-29 22:55:09
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
jpmorganpurchase.web.app: reCAPTCHA verification page
ai_description
PhishDestroy records the reCAPTCHA verification page captured at jpmorganpurchase.web.app, showing an IP address and a Google search URL.
ai_summary
The captured page at jpmorganpurchase.web.app presents a reCAPTCHA challenge asking the visitor to confirm they are not a robot. Below the checkbox, Ukrainian text explains that unusual traffic was detected from the visitor's computer network and that the page checks whether requests come from a person rather than a bot. The page also displays an IP address, a timestamp, and a URL pointing to a Google search query about covid. The stored VirusTotal domain result reports 12 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 22:43:27
revision
041b38966f4273300a789f4e726273ed03f6cf79e9d940165758d49cf371c050
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: 20 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
web.app
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
77
TLS
48
Waiting
67
Connection
51
Download
0
Response time, ms
243

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

DNS servers

Nameservers
  • IP address
    216.239.38.99
    Host
    ns4.googledomains.com
  • IP address
    216.239.32.99
    Host
    ns1.googledomains.com
  • IP address
    216.239.34.99
    Host
    ns2.googledomains.com
  • IP address
    216.239.36.99
    Host
    ns3.googledomains.com
DNS zone
web.app

Cookies

Cookies
  • Name
    __Secure-STRP
    Secure
    Yes
    SameSite
    Strict
  • Name
    SEARCH_SAMESITE
    SameSite
    Strict
  • Name
    AEC
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    NID
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

IP address
2620:0:890::100
ASN
54113
Organization
Fastly, Inc.
City
Mountain View
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
web.app

DNS records

A
  • 199.36.158.100
AAAA
  • 2620:0:890::100

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31556926; 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=31556926; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2620:0:890::100
IP version
6

Redirects

Redirect chain
  • https://jpmorganpurchase.web.app

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "web.app",
    "issuers": [
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 77,
        "tls": 48,
        "wait": 67,
        "connect": 51,
        "download": 0
    },
    "response_ms": 243
}
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": 919,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.38.99",
            "host": "ns4.googledomains.com"
        },
        {
            "ip": "216.239.32.99",
            "host": "ns1.googledomains.com"
        },
        {
            "ip": "216.239.34.99",
            "host": "ns2.googledomains.com"
        },
        {
            "ip": "216.239.36.99",
            "host": "ns3.googledomains.com"
        }
    ],
    "zone": "web.app"
}
Cookies
{
    "cookies": [
        {
            "name": "__Secure-STRP",
            "secure": true,
            "same_site": "Strict"
        },
        {
            "name": "SEARCH_SAMESITE",
            "same_site": "Strict"
        },
        {
            "name": "AEC",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "NID",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "2620:0:890::100",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "city": "Mountain View",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "web.app"
}
DNS records
{
    "A": [
        "199.36.158.100"
    ],
    "AAAA": [
        "2620:0:890::100"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31556926; 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=31556926; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2620:0:890::100",
    "family": 6
}
Redirects
{
    "chain": [
        "https://jpmorganpurchase.web.app"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
    }
}

Questions about jpmorganpurchase.web.app

Is jpmorganpurchase.web.app legit?

PhishDestroy records the reCAPTCHA verification page captured at jpmorganpurchase.web.app, showing an IP address and a Google search URL.

Is jpmorganpurchase.web.app safe to connect a wallet?

This report does not record which wallet requests jpmorganpurchase.web.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 jpmorganpurchase.web.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

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

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
jpmorganpurchase.web.app: caution — 12/92 VirusTotal engines. PhishDestroy risk score 96/100 (critical).
Social preview card jpmorganpurchase.web.app: caution — 12/92 VirusTotal engines. PhishDestroy risk score 96/100 (critical). v 121fdc547e91

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context United States199.36.158.100 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
Abuse contactcloud-abuse@google.com, network-abuse@google.com
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 10/1002 brand signals
Submitted URLhttp://jpmorganpurchase.web.app/
Favicon Hash
Observed page title
https://www.google.com/search?q=covid&sei=krzjauKhG-urxc8P7qGc8Qg
Automated brand references
Google Sei
TLS Certificate
Issued by Google Trust Services / WR4 · stored validity ends in 51 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States199.36.158.100
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
United StatesMountain View, US
Server header
scaffolding on HTTPServer2

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR4
Valid from
2026-09-23 17:59:58
Valid until
2026-12-22 17:59:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Certificate names · 2 SANs
  • web.app
  • *.web.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 · 199.36.158.100rapiddns.io

Latest Classified Outcome 2026-10-31 23:03:53 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 23:03:53 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:03:53 UTC last content: 2026-10-31 23:03:53 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
DNS8
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of jpmorganpurchase.web.app · checked Oct 29, 2026

80
Needs Work
Performance
FCP
1.14 s
First Contentful Paint
LCP
1.14 s
Largest Contentful Paint
CLS
0.023
Cumulative Layout Shift
TBT
852 ms
Total Blocking Time
SI
1.42 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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: 20 SHA-256 hashes: 18 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 21:39 UTC.

Open this scan on URLScan 01a18998-98d9-7208-9c9e-c4e902b3a922 ↗

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 observations12

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-01 00:03:53.000000
    Evidence SHA-256
    3a459be6e1803d4f1e5123513da739b29d3e5ba7ed02d46fbff8f2ca4a93164c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:03:53
    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-11-01 00:03:53.000000
    Evidence SHA-256
    3a459be6e1803d4f1e5123513da739b29d3e5ba7ed02d46fbff8f2ca4a93164c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:03:53
    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 12:04:18.000000
    Evidence SHA-256
    71b98a64a5b0afcdb8834a41953987907bf8aa22f40df12dba23e7d4a55ba357
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:18
    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 12:04:18.000000
    Evidence SHA-256
    71b98a64a5b0afcdb8834a41953987907bf8aa22f40df12dba23e7d4a55ba357
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:18
    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-31 00:58:03.000000
    Evidence SHA-256
    66e442262f689a827ee72476f9af9e6c33e24adf9187725ac9dc9883cbd3a0a7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:58:03
    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-31 00:58:03.000000
    Evidence SHA-256
    66e442262f689a827ee72476f9af9e6c33e24adf9187725ac9dc9883cbd3a0a7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:58:03
    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 13:10:25.000000
    Evidence SHA-256
    b5a1acbc73fb46a0b1ca36f0bbf50d5468162a70e9920be2b3d5fb3ea96772a4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:25
    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 13:10:25.000000
    Evidence SHA-256
    b5a1acbc73fb46a0b1ca36f0bbf50d5468162a70e9920be2b3d5fb3ea96772a4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:25
    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-30 01:23:49.000000
    Evidence SHA-256
    0ae22d609052a23440aeaa1e68cacc4daacc631326b0f11349fd2ab298bd9faf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:49
    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-30 01:23:49.000000
    Evidence SHA-256
    0ae22d609052a23440aeaa1e68cacc4daacc631326b0f11349fd2ab298bd9faf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:49
    Evidence reason
    alive_content
  11. 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 22:38:24.000000
    Evidence SHA-256
    6fb163f5bfc56aa9e6a11e6f60b15d35e3d20df5c39e88e83744ccb8cce13bac
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 22:38:24
    Evidence reason
  12. 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 22:38:24.000000
    Evidence SHA-256
    6fb163f5bfc56aa9e6a11e6f60b15d35e3d20df5c39e88e83744ccb8cce13bac
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 22:38:24
    Evidence reason

Threat Response Pipeline

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

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    jpmorganpurchase.web.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · Automated brand label: Chase Bank · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 12/92
  • Automated brand label: Chase Bank
    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

3 entries
  1. Added to PhishDestroy

    jpmorganpurchase.web.app

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    12/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

Check for cloaking

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

jpmorganpurchase.web.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including jpmorganpurchase.web.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/jpmorganpurchase.web.app"
  title="PhishDestroy threat report for jpmorganpurchase.web.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>