Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 20. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
magical-jelly-e5fdce.netlify.app favicon

magical-jelly-e5fdce.netlify.app

In short

magical-jelly-e5fdce.netlify.app is a Mastercard impersonation page detected by PhishDestroy on 2026-10-22. Risk: critical (100/100). Registrar: Netlify. Status: Content unavailable. Hosting: Amazon.com, Inc. VirusTotal: 20/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

“The Courier Guy”

Registrar
Netlify
Resolved IP
35.157.26.135
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
VirusTotal detections: 20/92 Automated brand label: Mastercard Scam type: Impersonation Google Safe Browsing: threat flag recorded
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Not recorded
Page captures
open gallery
Domain age
Not recorded
Reports sent
No sent record
Oct 23, 2026 CDN
X Telegram API
Source evidenceVirusTotal 20 / 92 · Google Safe Browsing: flagged 7 sources

VirusTotal

20 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
11
Suspicious
2
Undetected
30

Vendor labels

DNS8
suspicious
ESET
phishing
G-Data
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
suspicious
Gridinsoft
phishing
MalwareURL
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    120
    Type
    A
    Value
    18.208.88.157
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::259
  • TTL, seconds
    120
    Type
    A
    Value
    98.84.224.111
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::258

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial
cd5d0afb0611b5bd9d692535c0ca7c4
SHA-256
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Subject
*.netlify.app
Valid until
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar IANA ID
625
Registrar URL
http://www.name.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 11,
    "suspicious": 2,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "suspicious",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Name.com, Inc.
Created
2018-05-08T22:48:05Z
Expires
2025-05-08T22:48:05Z
Updated
2024-04-11T16:00:14Z
First seen
2026-10-21T21:08:28Z
DNS records
[
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    }
]
Dns at
2026-10-22T09:25:15Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "serial": "cd5d0afb0611b5bd9d692535c0ca7c4",
    "sha256": "bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478",
    "subject": "*.netlify.app",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2018-05-08T22:48:05Z",
    "updated": "2024-04-11T16:00:14Z",
    "expires": "2025-05-08T22:48:05Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 11 malicious + 2 suspicious / 92 · 2026-10-22 09:24:52 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-22T09:24:52Z
fetched_at
2026-10-22T23:29:54Z
stats
{"timeout":0,"harmless":49,"malicious":11,"suspicious":2,"undetected":30}

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a165c8-41f3-752b-83ba-66d6b4cac5c0

Final URL

https://magical-jelly-e5fdce.netlify.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://magical-jelly-e5fdce.netlify.app/
    From
    http://magical-jelly-e5fdce.netlify.app/
    Status
    307

IP address

18.208.88.157

Reverse DNS (PTR)

ec2-18-208-88-157.compute-1.amazonaws.com

Contacted domains

  • www.googletagmanager.com
  • connect.facebook.net

Contacted IP addresses

  • 142.251.110.97
  • 57.144.244.128
  • 18.208.88.157

Autonomous systems (ASN)

  • 15169
  • 32934
  • 14618

Server countries

  • US
  • DE

Linked domains

  • app.netlify.com

Document hash

bf8ffc4667a37d695f89a0e5a9d4d43d164ce1f2e2910c0671599820ebd00e14

Script hashes

  • 15a85882d4fe13515e30c3847668fa7d87d333397818469b8cad3f9960babe7d
  • 88fa6c7bd63b25cc72af6457ccbac715fab533e4b94136f72d6f25c71f02d7e7

JavaScript globals

  • dataLayer
  • fbq
  • _fbq
  • google_tag_data
  • google_tag_manager
  • onYouTubeIframeAPIReady

TLS session and certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Cipher
AES_128_GCM
Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

248

Certificate validity, days

396

Page requests

21

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • thecourierguy
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • The Courier Guy
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Netlify
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a165c8-41f3-752b-83ba-66d6b4cac5c0
Final url
https://magical-jelly-e5fdce.netlify.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://magical-jelly-e5fdce.netlify.app/",
        "from": "http://magical-jelly-e5fdce.netlify.app/",
        "status": 307
    }
]
Ip
18.208.88.157
Ptr
ec2-18-208-88-157.compute-1.amazonaws.com
Contacted domains
[
    "www.googletagmanager.com",
    "connect.facebook.net"
]
Contacted IP addresses
[
    "142.251.110.97",
    "57.144.244.128",
    "18.208.88.157"
]
Asns
[
    "15169",
    "32934",
    "14618"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "app.netlify.com"
]
Document hash
bf8ffc4667a37d695f89a0e5a9d4d43d164ce1f2e2910c0671599820ebd00e14
Script hashes
[
    "15a85882d4fe13515e30c3847668fa7d87d333397818469b8cad3f9960babe7d",
    "88fa6c7bd63b25cc72af6457ccbac715fab533e4b94136f72d6f25c71f02d7e7"
]
Globals
[
    "dataLayer",
    "fbq",
    "_fbq",
    "google_tag_data",
    "google_tag_manager",
    "onYouTubeIframeAPIReady"
]
Tls
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Domain age days
1
Apex age days
1
Tls age days
248
Tls valid days
396
Requests
21
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "thecourierguy"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "The Courier Guy"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Netlify",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
}
Separate monitor record · 2026-10-23 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a165c8-41f3-752b-83ba-66d6b4cac5c0
score
100
malicious
true
result_at
2026-10-23T03:30:30Z
enriched_at
2026-10-23T08:17:51Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:30","urlscan_enriched_at":"2026-10-23 10:17:51"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

100 / 100 · heuristic score · 3 brand references · 1 classifications

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

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-23T02:20:24Z
source_timestamp
2026-10-23 04:20:24
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
netlify.app
Allowed issuers
  • digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226

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
31647

Page title and metadata

Page title
The Courier Guy
Theme color
#ffffff

Trackers

Requests
20
Observed services
  • Name
    Facebook
    Company
    Meta
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google Tag
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Facebook Connect
    Company
    Meta
    Country
    US
    Category
    Site Analytics
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://connect.facebook.net/signals/config/813852727018572
  • https://www.googletagmanager.com/gtag/js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
5
TLS
11
Waiting
431
Connection
33
Download
35
Response time, ms
515

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
200186
CO₂, grams
0.0073
Cleaner than, %
7

DNS servers

Nameservers
  • IP address
    198.51.44.65
    Host
    dns3.p01.nsone.net
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
  • IP address
    198.51.45.1
    Host
    dns2.p01.nsone.net
DNS zone
netlify.app

Location

IP address
2a05:d014:58f:6200::259
ASN
16509
Organization
Amazon.com, Inc.
City
Frankfurt
Country
DE

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app

DNS records

A
  • 35.157.26.135
  • 63.176.8.218
AAAA
  • 2a05:d014:58f:6200::259
  • 2a05:d014:58f:6200::258

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

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

IP lookup

IP address
2a05:d014:58f:6200::258
IP version
6

Redirects

Redirect chain
  • https://magical-jelly-e5fdce.netlify.app

Technology stack

Technologies
  • Google Tag Manager
  • Google Analytics
  • Facebook Pixel
  • Google Font API
  • Netlify
  • HSTS
  • DigiCert
  • PWA

Page links

Internal links
1

HTTP headers

Response headers
Server
Netlify
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "netlify.app",
    "issuers": [
        "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-22T13:05:24Z",
    "first": "2026-10-22T13:05:24Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 31647
}
Page title and metadata
{
    "title": "The Courier Guy",
    "themeColor": "#ffffff"
}
Trackers
{
    "requests": 20,
    "trackers": [
        {
            "name": "Facebook",
            "company": "Meta",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google Tag",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Facebook Connect",
            "company": "Meta",
            "country": "US",
            "category": "Site Analytics",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://connect.facebook.net/signals/config/813852727018572",
        "https://www.googletagmanager.com/gtag/js"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 5,
        "tls": 11,
        "wait": 431,
        "connect": 33,
        "download": 35
    },
    "response_ms": 515
}
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": 200186,
    "co2_grams": 0.0073,
    "cleaner_than": 7
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.65",
            "host": "dns3.p01.nsone.net"
        },
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        },
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        },
        {
            "ip": "198.51.45.1",
            "host": "dns2.p01.nsone.net"
        }
    ],
    "zone": "netlify.app"
}
Location
{
    "ip": "2a05:d014:58f:6200::259",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Frankfurt",
    "country": "DE"
}
Ssl
{
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app"
}
DNS records
{
    "A": [
        "35.157.26.135",
        "63.176.8.218"
    ],
    "AAAA": [
        "2a05:d014:58f:6200::259",
        "2a05:d014:58f:6200::258"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; 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=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a05:d014:58f:6200::258",
    "family": 6
}
Redirects
{
    "chain": [
        "https://magical-jelly-e5fdce.netlify.app"
    ]
}
Tech stack
{
    "technologies": [
        "Google Tag Manager",
        "Google Analytics",
        "Facebook Pixel",
        "Google Font API",
        "Netlify",
        "HSTS",
        "DigiCert",
        "PWA"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=UTF-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
    }
}

Questions about magical-jelly-e5fdce.netlify.app

Is magical-jelly-e5fdce.netlify.app legit?

No. PhishDestroy classifies magical-jelly-e5fdce.netlify.app as a Mastercard impersonation page (risk: critical, 100/100); it was first detected on 2026-10-22. VirusTotal: 20/92 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.

Is magical-jelly-e5fdce.netlify.app safe to connect a wallet?

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

What should I do if I used magical-jelly-e5fdce.netlify.app?

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

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 8 captures

All capture links and hashes (8)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Thecourierguy report ↗
Google Safe Browsing Flagged Social engineering checked Oct 25, 2026
IP Context Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Netlify US(US)
Abuse contactabuse@netlify.com
Hosting abuse contact abuse@netlify.com Amazon.com, Inc. · AS16509
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 100/1003 brand signals
Submitted URLhttp://magical-jelly-e5fdce.netlify.app/
Favicon Hash
Observed page title
The Courier Guy
Automated brand references
Base Mastercard Visa
TLS Certificate
Issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 · stored validity ends in 144 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
35.157.26.135
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Frankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate names · 2 SANs
  • *.netlify.app
  • netlify.app

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

Latest Classified Outcome 2026-10-25 23:54:01 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-25 23:54:01 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 02:46:47 UTC last content: 2026-10-23 02:46:47 UTC current episode first observed: 2026-10-23 10:55:47 UTC observed RIP window: 2026-10-23 02:46:47 UTC → 2026-10-23 10:55:47 UTC · 8.15h midpoint estimate ≈ 2026-10-23 06:51:17 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

20 / 92 security vendors flagged this domain
View on VT
Last analyzed
Criminal IP
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
SOCRadar
Sophos
URLQuery
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://magical-jelly-e5fdce.netlify.app/
Final URL: https://magical-jelly-e5fdce.netlify.app/
The Courier Guy
Response
HTTP 200
HTML body
195.5 KB
Compressed
29.5 KB
Links
6 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: Netlify
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Accept-Ranges
bytes
Age
178
Cache-Control
public,max-age=0,must-revalidate
Cache-Status
"Netlify Edge"; hit; ttl=31535823
Content-Encoding
gzip
Content-Length
30764
Content-Type
text/html; charset=UTF-8
Date
Thu, 22 Oct 2026 13:05:02 GMT
Etag
"3315a3e7af96390f06a7252d27ff4908-ssl-df"
Server
Netlify
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Vary
Accept-Encoding
X-Nf-Request-Id
01M5HVE24QB1B1YRY03AZ279C3

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

Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
8.15
Estimate basis
Bounded by observations
Estimate precision
Medium

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history4

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→inactive

    http_no_content

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Domain monitor · First collection record

    Reachable

All retained availability observations16

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_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:54:01.000000
    Evidence SHA-256
    8c2c630739461e8b48882b957da9dbf8a0519083b2643d40e39c4f9520b1faf1
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 00:54:01
    Evidence reason
    http_other
  2. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:54:01.000000
    Evidence SHA-256
    8c2c630739461e8b48882b957da9dbf8a0519083b2643d40e39c4f9520b1faf1
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-26 00:54:01
    Evidence reason
    http_other
  3. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:56:03.000000
    Evidence SHA-256
    260e148c0fd73ea0956f27b422122fb2cead8f5c40f664dc78e0dde0902a7776
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 12:56:03
    Evidence reason
    http_other
  4. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:56:03.000000
    Evidence SHA-256
    260e148c0fd73ea0956f27b422122fb2cead8f5c40f664dc78e0dde0902a7776
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 12:56:03
    Evidence reason
    http_other
  5. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:44:22.000000
    Evidence SHA-256
    c006268fe69b48a169fc8e870c23607b14be531fb214fd0394142b8553af2d42
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 04:44:22
    Evidence reason
    http_other
  6. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:44:22.000000
    Evidence SHA-256
    c006268fe69b48a169fc8e870c23607b14be531fb214fd0394142b8553af2d42
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-25 04:44:22
    Evidence reason
    http_other
  7. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:46:54.000000
    Evidence SHA-256
    3b622d2bbd5f7065e94603f4a8aa2f29307dd56264b7c48ee2b6c4b24185050e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 12:46:54
    Evidence reason
    http_other
  8. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:46:54.000000
    Evidence SHA-256
    3b622d2bbd5f7065e94603f4a8aa2f29307dd56264b7c48ee2b6c4b24185050e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 12:46:54
    Evidence reason
    http_other
  9. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:49:17.000000
    Evidence SHA-256
    9e96c51f86bc33b56f39295c1590cf4d3514bd6539b633eca0ced93a225951fc
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 00:49:17
    Evidence reason
    http_other
  10. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:49:17.000000
    Evidence SHA-256
    9e96c51f86bc33b56f39295c1590cf4d3514bd6539b633eca0ced93a225951fc
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-24 00:49:17
    Evidence reason
    http_other
  11. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:55:47.000000
    Evidence SHA-256
    d42874e28aa17f81ad20e1972361f1b583e62ac569a767dbea9b7a01a6289a34
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-23 12:55:47
    Evidence reason
    http_other
  12. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:55:47.000000
    Evidence SHA-256
    d42874e28aa17f81ad20e1972361f1b583e62ac569a767dbea9b7a01a6289a34
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-23 12:55:47
    Evidence reason
    http_other
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:46:47.000000
    Evidence SHA-256
    800889c77bd380da6521078a4db18b141e5ac47e53046d9c3c3b75566d88c908
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 04:46:47
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:46:47.000000
    Evidence SHA-256
    800889c77bd380da6521078a4db18b141e5ac47e53046d9c3c3b75566d88c908
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 04:46:47
    Evidence reason
    alive_content
  15. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 00:44:29.000000
    Evidence SHA-256
    264233396d769d9de1ba071815c4e2fb54982fcb8a77bd6f2e66ff9a373fcd92
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 00:44:29
    Evidence reason
  16. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 00:44:29.000000
    Evidence SHA-256
    264233396d769d9de1ba071815c4e2fb54982fcb8a77bd6f2e66ff9a373fcd92
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 00:44:29
    Evidence reason

Recorded activity

5 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    20/92 engine detections

    View source
  3. Added to PhishDestroy

    magical-jelly-e5fdce.netlify.app

    View source
  4. URLScan

    Page captured

    View source
  5. Wayback Machine

    Page archived

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

Check for cloaking

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

magical-jelly-e5fdce.netlify.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Content unavailable
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.

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

Official reporting routes

Report to Your Local Authorities

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including magical-jelly-e5fdce.netlify.app)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/magical-jelly-e5fdce.netlify.app"
  title="PhishDestroy threat report for magical-jelly-e5fdce.netlify.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>