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

forum.wixstudio.com

In short

PhishDestroy stores a record for forum.wixstudio.com. Source observations are dated separately; missing checks do not establish safety.

“Community Support Forum | Wix Studio”

Review the evidence
Registrar
Wix.com
Resolved IP
United States184.105.99.43Civilized Discourse Construction Kit, Inc.
Registered
Dec 17, 2016
First observed
Oct 27, 2026
PhishDestroy assessment Critical
93/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 9/92
VirusTotal
9 / 92
engine detections ·
Page captures
3
open gallery
Domain age
3,605 days
registered 2016-12-17 according to RDAP · source data differ
Oct 27, 2026
X Telegram API

Questions about forum.wixstudio.com

Is forum.wixstudio.com legit?

PhishDestroy stores a record for forum.wixstudio.com. Source observations are dated separately; missing checks do not establish safety.

Is forum.wixstudio.com safe to connect a wallet?

This report does not record which wallet requests forum.wixstudio.com 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 forum.wixstudio.com?

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

Source evidenceVirusTotal 9 / 92 6 sources

VirusTotal

9 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
9
Suspicious
0
Undetected
29

Vendor labels

Bkav
malicious
DNS8
phishing
VIPRE
phishing
G-Data
phishing
Webroot
malicious
Gridinsoft
phishing
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing

Reputation score

0

Popularity ranks

Cisco Umbrella
934558

Registrar

GoDaddy.com, LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3343
    Type
    CNAME
    Value
    wix.hosted-by-discourse.com
  • TTL, seconds
    300
    Type
    MX
    Value
    mx-corp2.discoursemail.com
    Priority
    10
  • TTL, seconds
    3600
    Type
    CNAME
    Value
    wix.hosted-by-discourse.com
  • TTL, seconds
    2761
    Type
    CNAME
    Value
    wix.hosted-by-discourse.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2602:fd3f:3:ff01::2b
  • TTL, seconds
    300
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    417
    Type
    CNAME
    Value
    wix.hosted-by-discourse.com
  • TTL, seconds
    300
    Type
    MX
    Value
    mx-corp1.discoursemail.com
    Priority
    10
  • TTL, seconds
    300
    Type
    A
    Value
    184.105.99.43

DNS records observed

JARM fingerprint

29d29d15d29d29d00041d41d000000038eaaf490bec8dc33757f165ce01762

Certificate

Subject alternative names
  • forum.wixstudio.com
Issuer
Let's Encrypt / YR1
Serial
51951c5ff40e885bb691b53b0e70e5af166
SHA-256
7d6dbdcb9d151e9838a48f55633319979b968aee9b116492b38e3a32023bc553
Subject
forum.wixstudio.com
Valid until
Valid from

Registration record

Registrar
GoDaddy.com, LLC
Registrar IANA ID
146
Registrar URL
http://www.godaddy.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientRenewProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • dns1.p08.nsone.net
  • dns2.p08.nsone.net
  • dns3.p08.nsone.net
  • dns4.p08.nsone.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 9,
    "suspicious": 0,
    "undetected": 29
}
Vendor labels
{
    "Bkav": "malicious",
    "DNS8": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Webroot": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Popularity
{
    "Cisco Umbrella": 934558
}
Registrar
GoDaddy.com, LLC
Created
2016-12-17T19:23:35Z
Expires
2027-12-17T19:23:35Z
Updated
2024-05-01T08:41:12Z
First seen
2023-10-12T11:58:57Z
DNS records
[
    {
        "ttl": 3343,
        "type": "CNAME",
        "value": "wix.hosted-by-discourse.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx-corp2.discoursemail.com",
        "priority": 10
    },
    {
        "ttl": 3600,
        "type": "CNAME",
        "value": "wix.hosted-by-discourse.com"
    },
    {
        "ttl": 2761,
        "type": "CNAME",
        "value": "wix.hosted-by-discourse.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2602:fd3f:3:ff01::2b"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 417,
        "type": "CNAME",
        "value": "wix.hosted-by-discourse.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx-corp1.discoursemail.com",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "184.105.99.43"
    }
]
Dns at
2026-10-26T14:35:25Z
Jarm
29d29d15d29d29d00041d41d000000038eaaf490bec8dc33757f165ce01762
Certificate
{
    "san": [
        "forum.wixstudio.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "51951c5ff40e885bb691b53b0e70e5af166",
    "sha256": "7d6dbdcb9d151e9838a48f55633319979b968aee9b116492b38e3a32023bc553",
    "subject": "forum.wixstudio.com",
    "valid_to": "2026-12-11T00:01:34Z",
    "valid_from": "2026-09-12T00:01:35Z"
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146",
    "registrar_url": "http://www.godaddy.com",
    "created": "2016-12-17T19:23:35Z",
    "updated": "2024-05-01T08:41:12Z",
    "expires": "2027-12-17T19:23:35Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "dns1.p08.nsone.net",
        "dns2.p08.nsone.net",
        "dns3.p08.nsone.net",
        "dns4.p08.nsone.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 9 malicious + 0 suspicious / 92 · 2026-10-26 14:31:17 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-26T14:31:17Z
fetched_at
2026-10-27T00:44:02Z
stats
{"timeout":0,"harmless":54,"malicious":9,"suspicious":0,"undetected":29}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 cf7e5488a7d262500060abf1eb8af70a6b09b75b2ba7c923a19027a237fa8715

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a17a9a-b869-71dc-8322-0e0488c0ce2f

Final URL

https://forum.wixstudio.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://forum.wixstudio.com/
    From
    http://forum.wixstudio.com/
    Status
    307
  • To
    http://forum.wixstudio.com/
    From
    https://forum.wixstudio.com/
    Status
    307
  • To
    https://forum.wixstudio.com/
    From
    http://forum.wixstudio.com/
    Status
    301

IP address

184.105.99.43

Contacted domains

  • sea1.discourse-cdn.com
  • us1.discourse-cdn.com

Contacted IP addresses

  • 18.172.112.23
  • 65.8.131.2
  • 184.105.99.43

Autonomous systems (ASN)

  • 16509
  • 394230

Server countries

  • US

Linked domains

  • wix.com
  • www.discourse.org

Document hash

c928aa4651495c8c9444b5efe8adb349d09f9fa65615d4a3c2ec0b9ed9a69af2

TLS session and certificate

Subject alternative names
  • forum.wixstudio.com
Cipher
AES_128_GCM
Issuer
YR1
Subject
forum.wixstudio.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1186

Differs from the registration date in RDAP (2016-12-17), which gives 3600 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2632

Differs from the registration date in RDAP (2016-12-17), which gives 3600 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Certificate age, days

44

Certificate validity, days

89

Page requests

55

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000
Content-security-policy
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-Xcf0NmyplfHLg9HCvlCbdTKR6' 'strict-dynamic' 'wasm-unsafe-eval'; worker-src 'self' blob: https://us1.discourse-cdn.com/w
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Cross-origin-opener-policy
same-origin-allow-popups
Original source fields · JSON
Uuid
01a17a9a-b869-71dc-8322-0e0488c0ce2f
Final url
https://forum.wixstudio.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://forum.wixstudio.com/",
        "from": "http://forum.wixstudio.com/",
        "status": 307
    },
    {
        "to": "http://forum.wixstudio.com/",
        "from": "https://forum.wixstudio.com/",
        "status": 307
    },
    {
        "to": "https://forum.wixstudio.com/",
        "from": "http://forum.wixstudio.com/",
        "status": 301
    }
]
Ip
184.105.99.43
Contacted domains
[
    "sea1.discourse-cdn.com",
    "us1.discourse-cdn.com"
]
Contacted IP addresses
[
    "18.172.112.23",
    "65.8.131.2",
    "184.105.99.43"
]
Asns
[
    "16509",
    "394230"
]
Countries
[
    "US"
]
Linked domains
[
    "wix.com",
    "www.discourse.org"
]
Document hash
c928aa4651495c8c9444b5efe8adb349d09f9fa65615d4a3c2ec0b9ed9a69af2
Tls
{
    "san": [
        "forum.wixstudio.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "forum.wixstudio.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-11T00:01:34Z",
    "valid_from": "2026-09-12T00:01:35Z"
}
Domain age days
1186

Differs from the registration date in RDAP (2016-12-17), which gives 3600 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Apex age days
2632

Differs from the registration date in RDAP (2016-12-17), which gives 3600 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Tls age days
44
Tls valid days
89
Requests
55
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -96,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000",
    "content-security-policy": "upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-Xcf0NmyplfHLg9HCvlCbdTKR6' 'strict-dynamic' 'wasm-unsafe-eval'; worker-src 'self' blob: https://us1.discourse-cdn.com/w",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "cross-origin-opener-policy": "same-origin-allow-popups"
}
Separate monitor record · 2026-10-27 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17a9a-b869-71dc-8322-0e0488c0ce2f
score
0
malicious
false
result_at
2026-10-27T04:30:46Z
enriched_at
2026-10-27T09:15:43Z
source_timestamps
{"urlscan_result_at":"2026-10-27 05:30:46","urlscan_enriched_at":"2026-10-27 10:15:43"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

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

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-27T03:20:29Z
source_timestamp
2026-10-27 04:20:29
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Collected source details

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

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

Mail configuration

MX records
  • mx-corp1.discoursemail.com
  • mx-corp2.discoursemail.com
SPF lookups
0

CAA records

Count
1
Domain
forum.wixstudio.com
Allowed issuers
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
407
Archived days
499
Snapshots per day
0.43
Average page size, bytes
4554

Crawler rules

User agents
  • mauibot
  • semrushbot
  • ahrefsbot
  • blexbot
  • seo spider
Present
Yes
llms.txt file
Yes
Sitemap URLs
  • https://forum.wixstudio.com/sitemap.xml

Sitemap

Present
Yes
URL count
5000

Page title and metadata

Open Graph URL
https://forum.wixstudio.com/
Page title
Community Support Forum | Wix Studio
Open Graph type
website
Open Graph image
https://us1.discourse-cdn.com/wix/original/3X/1/3/1326609bd0b2f0038affb7422b34969656ada4f4.png
Open Graph title
Community Support Forum | Wix Studio
Generator
Discourse 2026.10.0-latest.1 - https://github.com/discourse/discourse version 0fcfb34131a0b743cb53134616a733cef7b4ec38
Open Graph site name
Community Support Forum | Wix Studio
Theme color
#ffffff
Description
Get expert help, troubleshoot design and code issues, and stay updated with other Studio creators in the Wix Studio Community support forum.
Twitter card
summary
Canonical URL
https://forum.wixstudio.com/
Open Graph description
Get expert help, troubleshoot design and code issues, and stay updated with other Studio creators in the Wix Studio Community support forum.

Forms and mixed content

Scripts without SRI
  • https://sea1.discourse-cdn.com/wix/extra-locales/2655d887cc617588017c74f2da24c88f30b92076/en/main.js
  • https://sea1.discourse-cdn.com/wix/extra-locales/0ffe7a21317d2af4f704e60d5a6802a6b9fa84f4/en/mf.js
  • https://sea1.discourse-cdn.com/wix/extra-locales/fb5e6aa3e1901e1bcd1fb376102aead93dc91952/en/overrides.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/d5ffcb03db88bb91c1cd62f3b81b91bffac3254c.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/a9a1b858441a761797b41c69fe2cf7079c6b3802.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/7ac2fe5507c9789029a7c98f8684e8e331e70927.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/a41d6ddc74853dd3eaa2e619fb39d809f35b75d1.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/0d1b6b72c34b57aecfe0d11e287b48002090b633.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/a9a1b6f9c0409542099b96676ff6fe60a988a6df.js
  • https://sea1.discourse-cdn.com/wix/theme-javascripts/9cbfac4ad15abce24636f6bb354536ba00ae64cf.js
Upgrades insecure requests
Yes
Third-party scripts
16

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
13
TLS
1368
Waiting
284
Connection
166
Download
1645
Response time, ms
3476

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
213484
CO₂, grams
0.0078
Cleaner than, %
6

DNS servers

Nameservers
  • IP address
    198.51.44.2
    Host
    dns1.p02.nsone.net
  • IP address
    198.51.45.2
    Host
    dns2.p02.nsone.net
  • IP address
    198.51.44.66
    Host
    dns3.p02.nsone.net
  • IP address
    198.51.45.66
    Host
    dns4.p02.nsone.net
DNS zone
wixstudio.com

Location

IP address
2602:fd3f:3:ff01::2b
ASN
394230
Organization
Civilized Discourse Construction Kit, Inc.
City
Seattle
Country
US

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
forum.wixstudio.com

DNS records

A
  • 184.105.99.43
MX
  • Mail server
    mx-corp1.discoursemail.com
    Priority
    10
  • Mail server
    mx-corp2.discoursemail.com
    Priority
    10
AAAA
  • 2602:fd3f:3:ff01::2b
CNAME
  • wix.hosted-by-discourse.com

DNSSEC

DS record
Yes
RRSIG
No
DNSKEY
Yes

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
0
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-996mrgw6GdJ1uz3bn3ZyLMFRg' 'strict-dyna
Strict-Transport-Security
max-age=31536000
Cross-Origin-Opener-Policy
same-origin-allow-popups
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2602:fd3f:3:ff01::2b
IP version
6

Redirects

Redirect chain
  • https://forum.wixstudio.com

Technology stack

Technologies
  • Discourse
  • Ruby
  • Ruby on Rails
  • Ember.js
  • Nginx
  • web-vitals
  • Moment.js
  • jQuery
  • HSTS
  • PWA
  • Open Graph

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000
Content-security-policy
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-OaBd9xAK97Pg0TxEt3oRBHJaX' 'strict-dynamic' 'wasm-unsafe-eval'; worker-src 'self' blob: https://us1.discourse-cdn.com/wix/assets/; frame-ancestors 'self'; manifest-src 'self'
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Cross-origin-opener-policy
same-origin-allow-popups
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mx-corp1.discoursemail.com",
        "mx-corp2.discoursemail.com"
    ],
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "forum.wixstudio.com",
    "issuers": [
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-09-23T23:07:10Z",
    "first": "2023-08-03T12:19:24Z",
    "changes": 407,
    "days_archived": 499,
    "scans_per_day": 0.43,
    "avg_page_bytes": 4554
}
Crawler rules
{
    "agents": [
        "mauibot",
        "semrushbot",
        "ahrefsbot",
        "blexbot",
        "seo spider"
    ],
    "present": true,
    "llms_txt": true,
    "sitemaps": [
        "https://forum.wixstudio.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5000
}
Page title and metadata
{
    "ogUrl": "https://forum.wixstudio.com/",
    "title": "Community Support Forum | Wix Studio",
    "ogType": "website",
    "ogImage": "https://us1.discourse-cdn.com/wix/original/3X/1/3/1326609bd0b2f0038affb7422b34969656ada4f4.png",
    "ogTitle": "Community Support Forum | Wix Studio",
    "generator": "Discourse 2026.10.0-latest.1 - https://github.com/discourse/discourse version 0fcfb34131a0b743cb53134616a733cef7b4ec38",
    "ogSiteName": "Community Support Forum | Wix Studio",
    "themeColor": "#ffffff",
    "description": "Get expert help, troubleshoot design and code issues, and stay updated with other Studio creators in the Wix Studio Community support forum.",
    "twitterCard": "summary",
    "canonicalUrl": "https://forum.wixstudio.com/",
    "ogDescription": "Get expert help, troubleshoot design and code issues, and stay updated with other Studio creators in the Wix Studio Community support forum."
}
Forms and mixed content
{
    "no_sri": [
        "https://sea1.discourse-cdn.com/wix/extra-locales/2655d887cc617588017c74f2da24c88f30b92076/en/main.js",
        "https://sea1.discourse-cdn.com/wix/extra-locales/0ffe7a21317d2af4f704e60d5a6802a6b9fa84f4/en/mf.js",
        "https://sea1.discourse-cdn.com/wix/extra-locales/fb5e6aa3e1901e1bcd1fb376102aead93dc91952/en/overrides.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/d5ffcb03db88bb91c1cd62f3b81b91bffac3254c.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/a9a1b858441a761797b41c69fe2cf7079c6b3802.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/7ac2fe5507c9789029a7c98f8684e8e331e70927.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/a41d6ddc74853dd3eaa2e619fb39d809f35b75d1.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/0d1b6b72c34b57aecfe0d11e287b48002090b633.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/a9a1b6f9c0409542099b96676ff6fe60a988a6df.js",
        "https://sea1.discourse-cdn.com/wix/theme-javascripts/9cbfac4ad15abce24636f6bb354536ba00ae64cf.js"
    ],
    "upgrade_insecure": true,
    "third_party_scripts": 16
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 13,
        "tls": 1368,
        "wait": 284,
        "connect": 166,
        "download": 1645
    },
    "response_ms": 3476
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 213484,
    "co2_grams": 0.0078,
    "cleaner_than": 6
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.2",
            "host": "dns1.p02.nsone.net"
        },
        {
            "ip": "198.51.45.2",
            "host": "dns2.p02.nsone.net"
        },
        {
            "ip": "198.51.44.66",
            "host": "dns3.p02.nsone.net"
        },
        {
            "ip": "198.51.45.66",
            "host": "dns4.p02.nsone.net"
        }
    ],
    "zone": "wixstudio.com"
}
Location
{
    "ip": "2602:fd3f:3:ff01::2b",
    "asn": "394230",
    "org": "Civilized Discourse Construction Kit, Inc.",
    "city": "Seattle",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "forum.wixstudio.com"
}
DNS records
{
    "A": [
        "184.105.99.43"
    ],
    "MX": [
        "{\"exchange\": \"mx-corp1.discoursemail.com\", \"priority\": 10}",
        "{\"exchange\": \"mx-corp2.discoursemail.com\", \"priority\": 10}"
    ],
    "AAAA": [
        "2602:fd3f:3:ff01::2b"
    ],
    "CNAME": [
        "wix.hosted-by-discourse.com"
    ]
}
Dnssec
{
    "ds": true,
    "rrsig": false,
    "dnskey": true
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": "0",
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-996mrgw6GdJ1uz3bn3ZyLMFRg' 'strict-dyna",
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": "same-origin-allow-popups",
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2602:fd3f:3:ff01::2b",
    "family": 6
}
Redirects
{
    "chain": [
        "https://forum.wixstudio.com"
    ]
}
Tech stack
{
    "technologies": [
        "Discourse",
        "Ruby",
        "Ruby on Rails",
        "Ember.js",
        "Nginx",
        "web-vitals",
        "Moment.js",
        "jQuery",
        "HSTS",
        "PWA",
        "Open Graph"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000",
        "content-security-policy": "upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-OaBd9xAK97Pg0TxEt3oRBHJaX' 'strict-dynamic' 'wasm-unsafe-eval'; worker-src 'self' blob: https://us1.discourse-cdn.com/wix/assets/; frame-ancestors 'self'; manifest-src 'self'",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin",
        "cross-origin-opener-policy": "same-origin-allow-popups"
    }
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://forum.wixstudio.com/
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
forum.wixstudio.com: caution — 11/92 VirusTotal engines. PhishDestroy risk score 93/100 (critical).
Social preview card forum.wixstudio.com: caution — 11/92 VirusTotal engines. PhishDestroy risk score 93/100 (critical). v c785dd6daa6f

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation United States184.105.99.43 abuse score 0/100 0 reports checked Oct 27, 2026 last reported
Registrar (base domain) Wix.com
Abuse contactabuse@wix.com, abuse@he.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wixstudio.com →
Registration (base domain)wixstudio.com · Created Dec 17, 2016 — Expires Dec 17, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 0/100
Submitted URLhttp://forum.wixstudio.com/
Favicon Hash
Observed page title
Community Support Forum | Wix Studio
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 40 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States184.105.99.43
Network ASN
AS394230
AS name
CDCK - Civilized Discourse Construction Kit, Inc., US
Organization
Civilized Discourse Construction Kit, Inc.
Observed location
United StatesSeattle, US
Server header
nginx

Mail routing 2 MX records

  • mx-corp1.discoursemail.com
  • mx-corp2.discoursemail.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-12 00:01:35
Valid until
2026-12-11 00:01:34
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7d6dbdcb9d151e9838a48f55633319979b968aee9b116492b38e3a32023bc553
Certificate names · 1 SAN
  • forum.wixstudio.com

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

viewdns.info · 184.105.99.43rapiddns.io

Latest Classified Outcome 2026-10-31 11:43:50 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: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 11:43:50 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:43:50 UTC last content: 2026-10-31 11:43:50 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

9 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Bkav
Chong Lua Dao
CyRadar
DNS8
G-Data
Gridinsoft
SOCRadar
VIPRE
Webroot
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 55 SHA-256 hashes: 52 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:55 UTC.

Open this scan on URLScan 01a17a9a-b869-71dc-8322-0e0488c0ce2f ↗

Stored observation history5

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations27

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
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:43:50.000000
    Evidence SHA-256
    7b1a0bb517115e20bba799fb6adc531d60a5a4f816249fb9acddecc0d1fcf096
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:43:50
    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-31 12:43:50.000000
    Evidence SHA-256
    7b1a0bb517115e20bba799fb6adc531d60a5a4f816249fb9acddecc0d1fcf096
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:43:50
    Evidence reason
    alive_content
  3. 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
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 04:24:49.000000
    Evidence SHA-256
    d9185ca453f2163ca8c822dfbcd1e95fb110f1170b3235f546b62992b5e73497
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 04:24:49
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 04:24:49.000000
    Evidence SHA-256
    d9185ca453f2163ca8c822dfbcd1e95fb110f1170b3235f546b62992b5e73497
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 04:24:49
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:40:30.000000
    Evidence SHA-256
    579ba37e27e810456de073b85cf6755d24da1b19a28d7fae7b8b828b8d436d2c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:40:30
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:40:30.000000
    Evidence SHA-256
    579ba37e27e810456de073b85cf6755d24da1b19a28d7fae7b8b828b8d436d2c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:40:30
    Evidence reason
    alive_content
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:48:18.000000
    Evidence SHA-256
    5667964fb5030f5752a90606282bc69b7c79d05aeec63e894ef920257840f925
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:48:18
    Evidence reason
    alive_content
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:48:18.000000
    Evidence SHA-256
    5667964fb5030f5752a90606282bc69b7c79d05aeec63e894ef920257840f925
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:48:18
    Evidence reason
    alive_content
  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-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:47:46.000000
    Evidence SHA-256
    3d6ef82119a5739b8a807dda3845b4cf761161699efdef5da388f81a024382a2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:47:46
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:47:46.000000
    Evidence SHA-256
    3d6ef82119a5739b8a807dda3845b4cf761161699efdef5da388f81a024382a2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:47:46
    Evidence reason
    alive_content
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-29 12:46:32.000000
    Evidence SHA-256
    d3aca4c660f92898db613cb28ef731f3e40d9cbf55c8e68bfcde8a6a7dd221c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:46:32
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:46:32.000000
    Evidence SHA-256
    d3aca4c660f92898db613cb28ef731f3e40d9cbf55c8e68bfcde8a6a7dd221c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:46:32
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-29 04:20:48.000000
    Evidence SHA-256
    5af2a9133677bdd9e77658ae618ef130151a6d715d7ec5ca48a5768db60b64df
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:20:48
    Evidence reason
    alive_content
  16. 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-29 04:20:48.000000
    Evidence SHA-256
    5af2a9133677bdd9e77658ae618ef130151a6d715d7ec5ca48a5768db60b64df
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 04:20:48
    Evidence reason
    alive_content
  17. 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-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-28 12:53:14.000000
    Evidence SHA-256
    18237583e55b308082ccea622c3d74c3e9583cd3a4ecaddbb916ad0fd234c567
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:53:14
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:53:14.000000
    Evidence SHA-256
    18237583e55b308082ccea622c3d74c3e9583cd3a4ecaddbb916ad0fd234c567
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:53:14
    Evidence reason
    alive_content
  20. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:53:47.000000
    Evidence SHA-256
    b5992be739e6df9230c72e5ccf4a75d6e37ce42cd24060c16c524929b015a425
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:53:47
    Evidence reason
    alive_content
  21. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:53:47.000000
    Evidence SHA-256
    b5992be739e6df9230c72e5ccf4a75d6e37ce42cd24060c16c524929b015a425
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:53:47
    Evidence reason
    alive_content
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:52:10.000000
    Evidence SHA-256
    5b30ff2d17b86b28bd7c5d084737c62f211ca07db9c166893ee08cf96792757e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:52:10
    Evidence reason
    alive_content
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:52:10.000000
    Evidence SHA-256
    5b30ff2d17b86b28bd7c5d084737c62f211ca07db9c166893ee08cf96792757e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:52:10
    Evidence reason
    alive_content
  24. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 04:45:50.000000
    Evidence SHA-256
    27de8d0a0539aeeddd6fd7c098b3db70aadb181905495b049e0a479fd4a7d928
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 04:45:50
    Evidence reason
    alive_content
  25. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 04:45:50.000000
    Evidence SHA-256
    27de8d0a0539aeeddd6fd7c098b3db70aadb181905495b049e0a479fd4a7d928
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 04:45:50
    Evidence reason
    alive_content
  26. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 00:47:24.000000
    Evidence SHA-256
    1913e1b51b55a73648c4498ec41b56731196edfaf98fb9d6e5c1856ab9963c09
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 00:47:24
    Evidence reason
  27. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 00:47:24.000000
    Evidence SHA-256
    1913e1b51b55a73648c4498ec41b56731196edfaf98fb9d6e5c1856ab9963c09
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 00:47:24
    Evidence reason

Threat Response Pipeline

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

Recorded events: 6. 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
    forum.wixstudio.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 4 of 4
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • VirusTotal
    Detections recorded on VirusTotal: 9/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. Added to PhishDestroy

    forum.wixstudio.com

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    9/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

Check for cloaking

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

forum.wixstudio.com

Evidence & External Reports

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

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

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