Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-01T16:22:02Z. Retrieved (as stored): 2026-11-01T18:52:35Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Redirect recorded vicesix.clubgoogle.com Details
Domain security and threat intelligence
vicesix.club favicon

vicesix.club

In short

PhishDestroy first recorded vicesix.club on 2026-10-31. Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-01T16:22:02Z. Retrieved (as stored): 2026-11-01T18:52:35Z.

Review the evidence
Registrar
SingaporeGname
Resolved IP
Canada104.21.2.34Cloudflare, Inc. · CDN
Registered
Oct 26, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 3/92 Young domain: 10 days old
VirusTotal
3 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 71
Page captures
2
open gallery
Domain age
10 days
registered 2026-10-26 according to WHOIS
OTX: 3 refs Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded vicesix.club on 2026-10-31. Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-01T16:22:02Z. Retrieved (as stored): 2026-11-01T18:52:35Z. Risk: critical (80/100). Registrar: Gname. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
3 / 92
Hosting
Canada104.21.2.34Cloudflare, Inc. · CDN
Registrar
SingaporeGname
Registered
Oct 26, 2026
OTX
3 community refs
Page captures
2
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for vicesix.club. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 3 / 92 · OTX 3 references 7 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
2
Suspicious
1
Undetected
34

Vendor labels

CRDF
malicious
Gridinsoft
phishing
alphaMountain.ai
suspicious

Reputation score

0

Registrar

Gname.com Pte. Ltd.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    roxy.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.2.34
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.128.169
  • TTL, seconds
    21600
    Type
    NS
    Value
    donovan.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    donovan.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.vicesix.club
  • vicesix.club
Issuer
Let's Encrypt / YE2
Serial
5befd4993334674781f7d864c96bc9c1224
SHA-256
41aa72e9605d58e8120dc6cbc1617b346685b3f32b223c462c0bdd3ba90e76e2
Subject
vicesix.club
Valid until
Valid from

Registration record

Registrar
Gname.com Pte. Ltd.
Registrar IANA ID
1923
Registrar URL
https://www.gname.com/
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
  • serverTransferProhibited
Nameservers
  • donovan.ns.cloudflare.com
  • roxy.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
  • server transfer prohibited
Registry events
Expiration
Registration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 2,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Registrar
Gname.com Pte. Ltd.
Created
2026-10-26T09:56:25Z
Expires
2027-10-26T09:56:25Z
Updated
2026-10-26T09:57:00Z
First seen
2026-10-26T10:08:47Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "roxy.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.2.34"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.128.169"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "donovan.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "donovan.ns.cloudflare.com"
    }
]
Dns at
2026-11-01T16:25:07Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.vicesix.club",
        "vicesix.club"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5befd4993334674781f7d864c96bc9c1224",
    "sha256": "41aa72e9605d58e8120dc6cbc1617b346685b3f32b223c462c0bdd3ba90e76e2",
    "subject": "vicesix.club",
    "valid_to": "2027-01-24T09:04:55Z",
    "valid_from": "2026-10-26T09:04:56Z"
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "registrar_iana_id": "1923",
    "registrar_url": "https://www.gname.com/",
    "created": "2026-10-26T09:56:25Z",
    "updated": "2026-10-26T09:57:00Z",
    "expires": "2027-10-26T09:56:25Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "donovan.ns.cloudflare.com",
        "roxy.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "server transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-26T09:56:25Z",
        "registration": "2026-10-26T09:56:25Z",
        "last update of RDAP database": "2026-10-26T09:57:01Z"
    }
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
5
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","CRDF","Forcepoint ThreatSeeker","Gridinsoft","VIPRE"]
observed_at
null
checked_at
2026-11-05 04:05:10
fetched_at
2026-11-05 03:05:10
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 71

SHA-256 039060d9119ea05954a37f1af0754a102376df1747a30a43bc9cd36881e529dc

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a1889b-9207-73a8-83c7-abbeb05dbdad

Final URL

https://vicesix.club/

HTTP response

666

Redirect type

https-only

Redirects

  • To
    https://vicesix.club/
    From
    http://vicesix.club/
    Status
    307
  • To
    http://vicesix.club/
    From
    https://vicesix.club/
    Status
    307
  • To
    https://vicesix.club/
    From
    http://vicesix.club/
    Status
    307

IP address

104.21.2.34

Contacted domains

  • www.google.com

Contacted IP addresses

  • 142.251.153.119
  • 104.21.2.34

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US

Document hash

c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea

Script hashes

  • 0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b

TLS session and certificate

Subject alternative names
  • *.vicesix.club
  • vicesix.club
Cipher
AES_128_GCM
Issuer
YE2
Subject
vicesix.club
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2

Registered domain age, days

2

Certificate age, days

3

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a1889b-9207-73a8-83c7-abbeb05dbdad
Final url
https://vicesix.club/
Status
666
Redirected
https-only
Redirects
[
    {
        "to": "https://vicesix.club/",
        "from": "http://vicesix.club/",
        "status": 307
    },
    {
        "to": "http://vicesix.club/",
        "from": "https://vicesix.club/",
        "status": 307
    },
    {
        "to": "https://vicesix.club/",
        "from": "http://vicesix.club/",
        "status": 307
    }
]
Ip
104.21.2.34
Contacted domains
[
    "www.google.com"
]
Contacted IP addresses
[
    "142.251.153.119",
    "104.21.2.34"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US"
]
Document hash
c396babd7f49262f18a3a2ec34542c8e314cb4d869875152bb9675a6bb6066ea
Script hashes
[
    "0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b"
]
Tls
{
    "san": [
        "*.vicesix.club",
        "vicesix.club"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "vicesix.club",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-24T09:04:55Z",
    "valid_from": "2026-10-26T09:04:56Z"
}
Domain age days
2
Apex age days
2
Tls age days
3
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 71,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-10-31 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1889b-9207-73a8-83c7-abbeb05dbdad
score
0
malicious
false
result_at
2026-10-31T04:30:24Z
enriched_at
2026-10-31T09:10:28Z
source_timestamps
{"urlscan_result_at":"2026-10-31 05:30:24","urlscan_enriched_at":"2026-10-31 10:10:28"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

c9895d89-f7a0-4118-b0af-5a33de851e57
Original source fields · JSON
Uuid
c9895d89-f7a0-4118-b0af-5a33de851e57

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-11-02T07:20:08Z

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-11-02T07:20:08Z
source_timestamp
2026-11-02 08:20:08
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: 15 fields

Mail configuration

SPF lookups
0

CAA records

Domain
vicesix.club

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    108.162.192.142
    Host
    roxy.ns.cloudflare.com
  • IP address
    108.162.195.114
    Host
    donovan.ns.cloudflare.com
DNS zone
vicesix.club

Location

IP address
172.67.128.169
ASN
13335
Organization
Cloudflare, Inc.
City
San Francisco
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
vicesix.club

DNS records

A
  • 172.67.128.169
  • 104.21.2.34
NS
  • donovan.ns.cloudflare.com
  • roxy.ns.cloudflare.com
SOA
Primary nameserver
donovan.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418507495
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
104.21.2.34
IP version
4

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • serverTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • roxy.ns.cloudflare.com
  • donovan.ns.cloudflare.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "vicesix.club"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.192.142",
            "host": "roxy.ns.cloudflare.com"
        },
        {
            "ip": "108.162.195.114",
            "host": "donovan.ns.cloudflare.com"
        }
    ],
    "zone": "vicesix.club"
}
Location
{
    "ip": "172.67.128.169",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "San Francisco",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "vicesix.club"
}
DNS records
{
    "A": [
        "172.67.128.169",
        "104.21.2.34"
    ],
    "NS": [
        "donovan.ns.cloudflare.com",
        "roxy.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"donovan.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418507495, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "104.21.2.34",
    "family": 4
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2026-10-26T09:56:25Z",
    "updated": "2026-10-26T09:57:00Z",
    "expires": "2027-10-26T09:56:25Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp",
        "serverTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "roxy.ns.cloudflare.com",
        "donovan.ns.cloudflare.com"
    ]
}

Questions about vicesix.club

Is vicesix.club legit?

PhishDestroy rates vicesix.club as critical risk (80/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-01T16:22:02Z. Retrieved (as stored): 2026-11-01T18:52:35Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is vicesix.club safe to connect a wallet?

This report does not record which wallet requests vicesix.club 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 vicesix.club?

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

URLScan · 2026-10-31 → www.google.com 1 / 2
SourceURLScan · 2026-10-31 → www.google.com
Recorded
StateStored capture
HTTP status200
Final URLhttps://www.google.com/chrome/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 79 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 71 report ↗
IP Context Canada104.21.2.34 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Gname SG(SG)
Abuse contact["complaint@gname.com", "f651612a2f356ad3s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for vicesix.club →
RegistrationCreated Oct 26, 2026 (10d · Very New!) — Expires Oct 26, 2027
Registrant countryGermany VirusTotal WHOIS
Registrant1f8f4166599d23eef651612a2f356ad3s@ VirusTotal WHOIS
WHOIS statusclientTransferProhibitedserverTransferProhibitedaddPeriod
HTTP Status301 Moved Permanently
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 2, 2026score 0/100
Submitted URLhttp://vicesix.club/
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.21.2.34
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • donovan.ns.cloudflare.com
  • roxy.ns.cloudflare.com

SOA

  • nsname: donovan.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418507495
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-26 09:04:56
Valid until
2027-01-24 09:04:55
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint41aa72e9605d58e8120dc6cbc1617b346685b3f32b223c462c0bdd3ba90e76e2
Certificate names · 2 SANs
  • *.vicesix.club
  • vicesix.club

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

viewdns.info · 104.21.2.34rapiddns.io

Latest Classified Outcome 2026-11-05 02:31:12 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-05 02:31:12 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 02:31:12 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
CRDF
Gridinsoft
alphaMountain.ai
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
Requested URL: http://vicesix.club/
Final URL: https://vicesix.club/
HTML body
5.3 KB
Compressed
2.7 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
CF-Cache-Status: DYNAMIC
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
CasT-Mode
default
cf-cache-status
DYNAMIC
CF-RAY
a52f877baedd840c-EWR
Connection
keep-alive
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 03:21:22 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=TRRkTl%2B5PFgx2FEn2M2x43D4DdVIcBAteWTBdn2A8NyVsQx7f8xxdQPepniCAsyZXq%2F5xROVbQZytJ1zIKcvL871KpCh2ty9gvnBpe0NL%2FUBkLCYgdpwCTML4CbbHRU%3D"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked

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

Archived
Registration & observation details2

Availability observations

Last reachable 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: 4 SHA-256 hashes: 3 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-31 03:25 UTC.

Open this scan on URLScan 01a1889b-9207-73a8-83c7-abbeb05dbdad ↗

Stored observation history6

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

    redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected

    http_redirect

  4. VirusTotal · Detection count

    2→3

    Engines added
    CRDF
    Engines removed
    None recorded
    Recorded vendor total
    3
  5. VirusTotal · Detection count

    1→2

    Engines added
    alphaMountain.ai
    Engines removed
    None recorded
    Recorded vendor total
    2
Earlier observations 1
  1. Availability monitor · Recorded state

    redirected

    http_redirect

All retained availability observations23

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. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-05 11:21:21.318386
    Evidence SHA-256
    547991b570db3c8269bee0185b7fa12df05c0b418f4b7a797fb4d0bb740e4f46
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 11:21:21.318386
    Evidence reason
  2. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:12.000000
    Evidence SHA-256
    61b68dbd3308936d8186682cdb208bafdc851fa9bade7ee9706d8b16b945789e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-05 03:31:12
    Evidence reason
    redirect
  3. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:12.000000
    Evidence SHA-256
    61b68dbd3308936d8186682cdb208bafdc851fa9bade7ee9706d8b16b945789e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-05 03:31:12
    Evidence reason
    redirect
  4. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:07:23.000000
    Evidence SHA-256
    b8f7b0b972160b01a60369299ee33be0c45d046c96b4553d3c1f4b5151f2f602
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-04 12:07:23
    Evidence reason
    redirect
  5. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:07:23.000000
    Evidence SHA-256
    b8f7b0b972160b01a60369299ee33be0c45d046c96b4553d3c1f4b5151f2f602
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-04 12:07:23
    Evidence reason
    redirect
  6. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-04 11:21:00.849465
    Evidence SHA-256
    94a9ae3d707b6cefa8168740bcb51c53137079a19bc0cd5bd77154e93c534a76
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 11:21:00.849465
    Evidence reason
  7. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-03 11:20:42.213040
    Evidence SHA-256
    7f511289ea6b6d1520a698f000d7fb3be1609f5f14dbf5ab5bf1c58eb4dbb974
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 11:20:42.213040
    Evidence reason
  8. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:00:43.000000
    Evidence SHA-256
    0c3ad4ad54a15a68718b71d0b15d99dcac54dfe8073b039ff3cb5aab3ee4e6fc
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-02 12:00:43
    Evidence reason
    redirect
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:00:43.000000
    Evidence SHA-256
    681c81d33ea242c8df89929302f772aecbee9aa0fe981906a324273c3cb31c38
    Evidence timestamp as recorded
    2026-11-02 12:00:43
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-02 11:20:40.834886
    Evidence SHA-256
    6b72dd67b3184766be6163de1e7b9604e36c85641b1d2618e2bdbe21069459a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 11:20:40.834886
    Evidence reason
  11. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:02:17.000000
    Evidence SHA-256
    4ac45a05473b4e2c3315a1de8269ccd85c5b02907b33a12bfef87e057d23d917
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-02 00:02:17
    Evidence reason
    redirect
  12. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:02:17.000000
    Evidence SHA-256
    4ac45a05473b4e2c3315a1de8269ccd85c5b02907b33a12bfef87e057d23d917
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-02 00:02:17
    Evidence reason
    redirect
  13. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:02:37.000000
    Evidence SHA-256
    c5b4cf825e998536bf1f951004e4c2cf761d10d405b2b8b42214b711c3778a53
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 12:02:37
    Evidence reason
    redirect
  14. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:02:37.000000
    Evidence SHA-256
    c5b4cf825e998536bf1f951004e4c2cf761d10d405b2b8b42214b711c3778a53
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 12:02:37
    Evidence reason
    redirect
  15. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-01 11:20:10.198716
    Evidence SHA-256
    b2987bb7a7acc32f1f9011b7a56a5a9a8539c203c0dded9abde43c0e22a9adeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 11:20:10.198716
    Evidence reason
  16. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:45:35.000000
    Evidence SHA-256
    a8841ccb2e668ed1e3f6a5861894d7f974cc37d73d9d06a8c460bff5a58350c1
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 03:45:35
    Evidence reason
    redirect
  17. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:45:35.000000
    Evidence SHA-256
    a8841ccb2e668ed1e3f6a5861894d7f974cc37d73d9d06a8c460bff5a58350c1
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 03:45:35
    Evidence reason
    redirect
  18. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:00:22.000000
    Evidence SHA-256
    2f302c55c980cb5b71f76a736a7e71912626b18f6144be6f7531324e2ff76968
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:00:22
    Evidence reason
    redirect
  19. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:00:22.000000
    Evidence SHA-256
    2f302c55c980cb5b71f76a736a7e71912626b18f6144be6f7531324e2ff76968
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:00:22
    Evidence reason
    redirect
  20. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:00:19.000000
    Evidence SHA-256
    396363653458dfb14dfc42d2756e697b59d563f9ca36878ead0c339313dbfebf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:00:19
    Evidence reason
    redirect
  21. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:00:19.000000
    Evidence SHA-256
    396363653458dfb14dfc42d2756e697b59d563f9ca36878ead0c339313dbfebf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:00:19
    Evidence reason
    redirect
  22. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  23. 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-31 04:59:20.230176
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 11. 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
    vicesix.club detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 · VirusTotal detections +1 Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 71
  • 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: 3/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +1
    New detections: +1 (2 → 3): CRDF
  • VirusTotal detections +1
    New detections: +1 (1 → 2): alphaMountain.ai
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

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    3/92 engine detections

    View source
  3. Added to PhishDestroy

    vicesix.club

    View source
  4. URLScan

    Malicious · engine verdict · score 71

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
All stored records by source

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

Download all records as JSON

Check for cloaking

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

vicesix.club

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 3 refs 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?

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.

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 vicesix.club)
  • 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.

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/vicesix.club"
  title="PhishDestroy threat report for vicesix.club"
  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>