Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
crimson-clutch.shop favicon

crimson-clutch.shop

In short

crimson-clutch.shop is a phishing page detected by PhishDestroy on 2026-10-25.

“Błąd - Ulla Popken”

Registrar
Spaceship
Resolved IP
34.8.77.192
Registered
Aug 6, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 16/92 Spamhaus DBL: phishing domain
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Page captures
open gallery
Domain age
Reports sent
No sent record
OTX: 3 refs Oct 25, 2026
X Telegram API

Analysis

Domain summary

crimson-clutch.shop is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Spaceship. Status: Last known active. Hosting: Google LLC. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
16 / 92
OTX
3 community refs
Page captures
4

PhishDestroy threat report

Overview

PhishDestroy classifies crimson-clutch.shop as a suspicious domain based on multiple security vendor detections. The domain was first seen by PhishDestroy on 2026-10-25. The recorded page title is "Błąd - Ulla Popken". An HTTP request on that date returned a 200 status code.

How the scam works

The domain is flagged because several security vendors label it as phishing or malicious, a common risk where deceptive pages are used to harvest credentials or personal data. No phishing form or malicious payload was observed on the captured page, so the specific mechanism remains unverified.

Evidence

VirusTotal reported 12 malicious and 4 suspicious detections from 92 engines on 2026-10-20, with vendors such as BitDefender, ESET and Sophos marking it phishing. Google Safe Browsing checked the URL on 2026-10-25 and did not flag it. Cloudflare Radar scanned the site on 2026-10-25 and returned a malicious verdict in the malware category. urlscan.io captured the site on 2026-08-16, gave an overall clean verdict but its engine score was 91 and flagged it as malicious; the scan showed a 307 redirect to HTTPS and a final 200 response. OTX listed three pulses mentioning the domain.

Infrastructure

The recorded IP was 34.8.77.192, belonging to Google LLC in the United States, and the HTTP response header listed nginx as the server. The domain was registered eight days before the first VirusTotal sighting and uses a TLS certificate issued by Google Trust Services, valid for 90 days. Authoritative nameservers were ns1.dnsip.com and ns2.dnsip.com, with no DNSSEC records observed.

What to do

Visitors should treat the site as suspicious and avoid entering any credentials or personal information. Organizations can block the domain at network perimeters and monitor logs for connections to crimson-clutch.shop. Since no credential capture was confirmed, password changes are only needed if users have already submitted data.

Source evidenceVirusTotal 16 / 92 · OTX 3 references 8 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
12
Suspicious
4
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
spam
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.dnsip.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.dnsip.com
  • TTL, seconds
    600
    Type
    A
    Value
    34.8.77.192
  • TTL, seconds
    600
    Type
    SOA
    Responsible mailbox
    dnsadmin.dnsip.com
    Value
    ns1.dnsip.com

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84

Certificate

Subject alternative names
  • crimson-clutch.shop
Issuer
Google Trust Services / WR3
Serial
70816477ce73e34b1229a1a57524cb5
SHA-256
e3b701c9a15b660822dfa217fac4515d8090ee1e6fe5628e459f16b8a0c3ae0e
Subject
crimson-clutch.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 12,
    "suspicious": 4,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
First seen
2026-08-10T13:32:05Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.dnsip.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.dnsip.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "34.8.77.192"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "dnsadmin.dnsip.com",
        "value": "ns1.dnsip.com"
    }
]
Dns at
2026-10-19T23:31:58Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "crimson-clutch.shop"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "70816477ce73e34b1229a1a57524cb5",
    "sha256": "e3b701c9a15b660822dfa217fac4515d8090ee1e6fe5628e459f16b8a0c3ae0e",
    "subject": "crimson-clutch.shop",
    "valid_to": "2027-01-04T01:16:25Z",
    "valid_from": "2026-10-06T00:22:13Z"
}
Separate source record · 12 malicious + 4 suspicious / 92 · 2026-10-19 23:31:45 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-19T23:31:45Z
fetched_at
2026-10-25T02:20:50Z
stats
{"timeout":0,"harmless":44,"malicious":12,"suspicious":4,"undetected":32}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

60b96107-7ff1-403f-9d73-30e699ba14fc

Final URL

https://crimson-clutch.shop/

HTTP response

200

Navigation history

  • URL
    https://crimson-clutch.shop/
    Status
    200

DOM structure hash

cb4accf9f3be723809f7b2f54e0681af1a95c8db0233b353f8b1ae3801695e6a

Document hash

d0ae424415cbfd302e074b237ec66c004e142512e5bd43693f7d5fbec607491a

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    crimson-clutch.shop
    Type
    A
    Value
    34.8.77.192

DNSSEC valid

No

IP address

34.8.77.192

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware
Original source fields · JSON
Uuid
60b96107-7ff1-403f-9d73-30e699ba14fc
Final url
https://crimson-clutch.shop/
Status
200
History
[
    {
        "url": "https://crimson-clutch.shop/",
        "status": 200
    }
]
DOM structure hash
cb4accf9f3be723809f7b2f54e0681af1a95c8db0233b353f8b1ae3801695e6a
Document hash
d0ae424415cbfd302e074b237ec66c004e142512e5bd43693f7d5fbec607491a
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "crimson-clutch.shop",
        "type": "A",
        "value": "34.8.77.192"
    }
]
Dnssec valid
false
Ip
34.8.77.192
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 91

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a0091c-bf80-71de-9272-fc6f4ea17bf7

Final URL

https://crimson-clutch.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://crimson-clutch.shop/
    From
    http://crimson-clutch.shop/
    Status
    307

IP address

34.8.77.192

Reverse DNS (PTR)

192.77.8.34.bc.googleusercontent.com

Contacted IP addresses

  • 34.8.77.192

Autonomous systems (ASN)

  • 396982

Server countries

  • US

Document hash

6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

JavaScript globals

  • fence

TLS session and certificate

Subject alternative names
  • crimson-clutch.shop
Cipher
AES_128_GCM
Issuer
WR3
Subject
crimson-clutch.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

8

Registered domain age, days

8

Certificate age, days

1

Certificate validity, days

90

Page requests

2

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a0091c-bf80-71de-9272-fc6f4ea17bf7
Final url
https://crimson-clutch.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://crimson-clutch.shop/",
        "from": "http://crimson-clutch.shop/",
        "status": 307
    }
]
Ip
34.8.77.192
Ptr
192.77.8.34.bc.googleusercontent.com
Contacted IP addresses
[
    "34.8.77.192"
]
Asns
[
    "396982"
]
Countries
[
    "US"
]
Document hash
6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d
Globals
[
    "fence"
]
Tls
{
    "san": [
        "crimson-clutch.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR3",
    "subject": "crimson-clutch.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-12T07:51:44Z",
    "valid_from": "2026-08-14T06:56:51Z"
}
Domain age days
8
Apex age days
8
Tls age days
1
Tls valid days
90
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 91,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a0091c-bf80-71de-9272-fc6f4ea17bf7
score
0
malicious
false
result_at
2026-10-25T04:30:49Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:49","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T02:27:40Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-25T02:27:40Z
source_timestamp
2026-10-25 03:27:40
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
crimson-clutch.shop — Suspicious Domain
ai_description
PhishDestroy lists crimson-clutch.shop as a suspicious domain after multiple security vendors flagged it as malicious, despite the page title showing an error.
ai_generated_at
2026-10-25T02:27:11Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
crimson-clutch.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.07
Average page size, bytes
49790

Page title and metadata

Page title
Błąd - Ulla Popken

Trackers

Requests
8
Observed services
  • Name
    Facebook
    Company
    Meta
    Country
    US
    Category
    Advertising
    Requests
    2
  • Name
    Facebook Connect
    Company
    Meta
    Country
    US
    Category
    Site Analytics
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
611
TLS
34
Waiting
411
Connection
11
Download
38
Response time, ms
1105

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
415794
CO₂, grams
0.0152
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    218.98.111.202
    Host
    ns1.dnsip.com
  • IP address
    211.99.99.29
    Host
    ns2.dnsip.com
DNS zone
crimson-clutch.shop

Cookies

Cookies
  • Name
    _bcazhz_vid
  • Name
    _bcazhz_cvid
  • Name
    _bcazhz_vs
  • Name
    currency_code
    Session cookie
    Yes
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    _BAIHEBG_ua
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHEBG_pu
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHEBG_tz
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHEBG_ss
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHEBG_lang
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHEBG_vs
    Secure
    Yes
    SameSite
    None
  • Name
    _BAIHEBG_dt
    Secure
    Yes
    SameSite
    None
  • Name
    _fbp
    SameSite
    Lax

Location

IP address
34.8.77.192
ASN
396982
Organization
Google LLC
City
Kansas City
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
crimson-clutch.shop

DNS records

A
  • 34.8.77.192
NS
  • ns1.dnsip.com
  • ns2.dnsip.com
SOA
Primary nameserver
ns1.dnsip.com
Hostmaster
dnsadmin.dnsip.com
Serial
1785989598
Refresh, seconds
3600
Retry, seconds
300
Expiry, seconds
1209600
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

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

IP lookup

IP address
34.8.77.192
IP version
4

Redirects

Redirect chain
  • https://crimson-clutch.shop

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "crimson-clutch.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T00:45:02Z",
    "first": "2026-10-10T23:16:44Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.07,
    "avg_page_bytes": 49790
}
Page title and metadata
{
    "title": "Błąd - Ulla Popken"
}
Trackers
{
    "requests": 8,
    "trackers": [
        {
            "name": "Facebook",
            "company": "Meta",
            "country": "US",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "Facebook Connect",
            "company": "Meta",
            "country": "US",
            "category": "Site Analytics",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 611,
        "tls": 34,
        "wait": 411,
        "connect": 11,
        "download": 38
    },
    "response_ms": 1105
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 415794,
    "co2_grams": 0.0152,
    "cleaner_than": 1
}
Dns server
{
    "ns": [
        {
            "ip": "218.98.111.202",
            "host": "ns1.dnsip.com"
        },
        {
            "ip": "211.99.99.29",
            "host": "ns2.dnsip.com"
        }
    ],
    "zone": "crimson-clutch.shop"
}
Cookies
{
    "cookies": [
        {
            "name": "_bcazhz_vid"
        },
        {
            "name": "_bcazhz_cvid"
        },
        {
            "name": "_bcazhz_vs"
        },
        {
            "name": "currency_code",
            "session": true
        },
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "_BAIHEBG_ua",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHEBG_pu",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHEBG_tz",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHEBG_ss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHEBG_lang",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHEBG_vs",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BAIHEBG_dt",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_fbp",
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "34.8.77.192",
    "asn": "396982",
    "org": "Google LLC",
    "city": "Kansas City",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "crimson-clutch.shop"
}
DNS records
{
    "A": [
        "34.8.77.192"
    ],
    "NS": [
        "ns1.dnsip.com",
        "ns2.dnsip.com"
    ],
    "SOA": "{\"nsname\": \"ns1.dnsip.com\", \"hostmaster\": \"dnsadmin.dnsip.com\", \"serial\": 1785989598, \"refresh\": 3600, \"retry\": 300, \"expire\": 1209600, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "34.8.77.192",
    "family": 4
}
Redirects
{
    "chain": [
        "https://crimson-clutch.shop"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware

Questions about crimson-clutch.shop

Is crimson-clutch.shop legit?

No. PhishDestroy classifies crimson-clutch.shop as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is crimson-clutch.shop safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on crimson-clutch.shop. 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 crimson-clutch.shop?

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 · 4 captures

All capture links and hashes (4)
Observed page title
Błąd - Ulla Popken
TLS Certificate
Issued by Google Trust Services / WR3 · stored validity ends in 69 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
RegistrationCreated Aug 6, 2026 (81d · New) — Expires Aug 6, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 98/100
Submitted URLhttp://crimson-clutch.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
34.8.77.192
Network ASN
AS396982
Organization
Google LLC
Observed location
Kansas City, US
Server header
nginx

Nameservers 2

  • ns1.dnsip.com
  • ns2.dnsip.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR3
Valid from
2026-10-06 00:22:13
Valid until
2027-01-04 01:16:25
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte3b701c9a15b660822dfa217fac4515d8090ee1e6fe5628e459f16b8a0c3ae0e
Certificate names · 1 SAN
  • crimson-clutch.shop

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:00:51 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-25 23:00:51 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 02:00:43 UTC last content: 2026-10-25 02:00:43 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 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of crimson-clutch.shop · checked Oct 25, 2026

75
Needs Work
Performance
FCP
2.41 s
First Contentful Paint
LCP
5.12 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
188 ms
Total Blocking Time
SI
3 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://crimson-clutch.shop/
Final URL: https://crimson-clutch.shop/
Błąd - Ulla Popken
Response
HTTP 200
HTML body
406.1 KB
Compressed
79.4 KB
Links
0 internal · 0 external
Detected technologies
vuenginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Alt-Svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 00:44:02 GMT
execution-time
0.0397160053
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 google

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

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.

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

All retained availability observations7

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:51.000000
    Evidence SHA-256
    9c79cee9cf8193cd0bc9e17103059599c46f81626ab056ba49fb07f58f5452e9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:51
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:51.000000
    Evidence SHA-256
    9c79cee9cf8193cd0bc9e17103059599c46f81626ab056ba49fb07f58f5452e9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:51
    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-25 12:00:58.000000
    Evidence SHA-256
    34b4c668067007feab2813838eeaa74a5b1887a5fbb9a6f0dda0ac6df6fcc922
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:58
    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-25 12:00:58.000000
    Evidence SHA-256
    34b4c668067007feab2813838eeaa74a5b1887a5fbb9a6f0dda0ac6df6fcc922
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:58
    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-25 03:00:43.000000
    Evidence SHA-256
    d193313f402db954542318c5bbf03cd2d52c3cfc29ffce4d70a6e4338b50c9cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:00:43
    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-25 03:00:43.000000
    Evidence SHA-256
    d193313f402db954542318c5bbf03cd2d52c3cfc29ffce4d70a6e4338b50c9cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:00:43
    Evidence reason
    alive_content
  7. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 02:45:30.799168
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Recorded activity

6 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    16/92 engine detections

    View source
  3. Added to PhishDestroy

    crimson-clutch.shop

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Cloudflare Radar

    Phishing

    View source
  6. URLScan

    Malicious · engine verdict · score 91

    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.

crimson-clutch.shop

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

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

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 crimson-clutch.shop)
  • 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.

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.

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/crimson-clutch.shop"
  title="PhishDestroy threat report for crimson-clutch.shop"
  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>