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

wedks.com

In short

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

“WEBUCCC”

Review the evidence
Registrar
SingaporeGname
Resolved IP
United States23.20.116.56Amazon.com
Registered
Nov 3, 2025
First observed
Oct 26, 2026
PhishDestroy assessment Critical
93/100
Evidence score
First observed Oct 26, 2026 11:40 UTC · PhishDestroy
Risk signals
VirusTotal detections: 12/92
VirusTotal
12 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 93
Cloudflare Radar
Phishing
Page captures
10
open gallery
Domain age
362 days
registered 2025-11-03 according to WHOIS · source data differ
Reports sent
1
view timeline
OTX: 1 ref Oct 26, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is complaint@gname.com. The latest stored availability evidence still shows the domain reachable; 5 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
5 days
Reports sent
1
Latest case ID
PD-20261026-C794F3
Current status
Observed active at latest stored check

Questions about wedks.com

Is wedks.com legit?

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

Is wedks.com safe to connect a wallet?

This report does not record which wallet requests wedks.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 wedks.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 12 / 92 · OTX 1 references 8 sources

VirusTotal

12 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
12
Suspicious
0
Undetected
33

Vendor labels

CRDF
malicious
G-Data
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
Kaspersky
phishing
Gridinsoft
phishing
MalwareURL
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    charles.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    gracie.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    charles.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    23.20.116.56

DNS records observed

JARM fingerprint

21d19d00021d21d00042d43d0000005ad20eceaf7f71ae0887d2ff117bf97f

Certificate

Subject alternative names
  • webttt555.shop
  • www.webttt555.shop
Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Serial
c5cac7fe678f8b0fbc95b366ceb7e048
SHA-256
fd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775
Subject
webttt555.shop
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Registration
Last RDAP database update
Registrar
Gname.com Pte. Ltd.
Registrar IANA ID
1923
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2025-11-03T00:00:00Z
Updated
2025-11-03T00:00:00Z
First seen
2023-10-11T17:27:10Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "charles.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "gracie.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "charles.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "23.20.116.56"
    }
]
Dns at
2026-10-26T01:34:21Z
Jarm
21d19d00021d21d00042d43d0000005ad20eceaf7f71ae0887d2ff117bf97f
Certificate
{
    "san": [
        "webttt555.shop",
        "www.webttt555.shop"
    ],
    "issuer": "Sectigo Limited / Sectigo Public Server Authentication CA DV R36",
    "serial": "c5cac7fe678f8b0fbc95b366ceb7e048",
    "sha256": "fd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775",
    "subject": "webttt555.shop",
    "valid_to": "2027-03-14T23:59:59Z",
    "valid_from": "2026-08-28T00:00:00Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-11-03T04:34:59Z",
        "registration": "2025-11-03T04:34:59Z",
        "last update of RDAP database": "2026-10-24T16:33:48Z"
    },
    "registrar": "Gname.com Pte. Ltd.",
    "registrar_iana_id": "1923"
}
Separate source record · 12 malicious + 0 suspicious / 92 · 2026-10-26 01:05:11 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-26T01:05:11Z
fetched_at
2026-10-26T14:13:40Z
stats
{"timeout":0,"harmless":47,"malicious":12,"suspicious":0,"undetected":33}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

0a86d3a7-5fa2-4bc8-b88c-30a06a3029d4

Final URL

https://wedks.com/

Navigation history

  • URL
    https://wedks.com/
    Status
    0

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    wedks.com
    Type
    A
    Value
    23.20.116.56

DNSSEC valid

No

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Updated
Expires
Nameservers
  • charles.ns.cloudflare.com
  • gracie.ns.cloudflare.com
Original source fields · JSON
Uuid
0a86d3a7-5fa2-4bc8-b88c-30a06a3029d4
Final url
https://wedks.com/
History
[
    {
        "url": "https://wedks.com/",
        "status": 0
    }
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "wedks.com",
        "type": "A",
        "value": "23.20.116.56"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2025-11-03T04:34:59Z",
    "updated": "2026-10-24T16:30:56Z",
    "expires": "2027-11-03T04:34:59Z",
    "nameservers": [
        "charles.ns.cloudflare.com",
        "gracie.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 93

SHA-256 87037fb0340a340111c0e8a0fe647968f70be2892039539b29d68f843437f780

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a17812-6bf6-77b8-8105-7a815941c0ad

Final URL

https://wedks.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://wedks.com/
    From
    http://wedks.com/
    Status
    307

IP address

23.20.116.56

Reverse DNS (PTR)

ec2-23-20-116-56.compute-1.amazonaws.com

Contacted IP addresses

  • 23.20.116.56

Autonomous systems (ASN)

  • 14618

Server countries

  • US

Document hash

508757cdd4d4fbc2b855c74a78ba3b1f0eb59314dfd18f85db88b15bb3f2054c

Script hashes

  • 8e89fcb524218901b5fe4b302ec9e9f8591580426d964936f74e0c35f22e755f
  • dfe11c34cb98c6e3ff6674130049a0922b72ef3b6604982edc4b45d205635557

JavaScript globals

  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • __vueuse_ssr_handlers__
  • __VUE__
  • __vite_is_modern_browser

Browser storage keys

  • topActive

TLS session and certificate

Subject alternative names
  • webttt555.shop
  • www.webttt555.shop
Cipher
AES_128_GCM
Issuer
Sectigo Public Server Authentication CA DV R36
Subject
webttt555.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1739

Differs from the registration date in WHOIS (2025-11-03), which gives 357 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1739

Differs from the registration date in WHOIS (2025-11-03), which gives 357 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Certificate age, days

59

Certificate validity, days

198

Page requests

7

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a17812-6bf6-77b8-8105-7a815941c0ad
Final url
https://wedks.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://wedks.com/",
        "from": "http://wedks.com/",
        "status": 307
    }
]
Ip
23.20.116.56
Ptr
ec2-23-20-116-56.compute-1.amazonaws.com
Contacted IP addresses
[
    "23.20.116.56"
]
Asns
[
    "14618"
]
Countries
[
    "US"
]
Document hash
508757cdd4d4fbc2b855c74a78ba3b1f0eb59314dfd18f85db88b15bb3f2054c
Script hashes
[
    "8e89fcb524218901b5fe4b302ec9e9f8591580426d964936f74e0c35f22e755f",
    "dfe11c34cb98c6e3ff6674130049a0922b72ef3b6604982edc4b45d205635557"
]
Globals
[
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__vueuse_ssr_handlers__",
    "__VUE__",
    "__vite_is_modern_browser"
]
Storage keys
[
    "topActive"
]
Tls
{
    "san": [
        "webttt555.shop",
        "www.webttt555.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "Sectigo Public Server Authentication CA DV R36",
    "subject": "webttt555.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2027-03-14T23:59:59Z",
    "valid_from": "2026-08-28T00:00:00Z"
}
Domain age days
1739

Differs from the registration date in WHOIS (2025-11-03), which gives 357 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Apex age days
1739

Differs from the registration date in WHOIS (2025-11-03), which gives 357 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Tls age days
59
Tls valid days
198
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a1772c-55f9-736a-97be-799771e0f790
score
null
malicious
null
result_at
null
enriched_at
2026-10-27T09:21:50Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-27 10:21:50"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

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: 11 fields

Mail configuration

SPF lookups
0

CAA records

Domain
wedks.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

DNS servers

Nameservers
  • IP address
    172.64.33.83
    Host
    charles.ns.cloudflare.com
  • IP address
    108.162.194.144
    Host
    gracie.ns.cloudflare.com
DNS zone
wedks.com

Location

IP address
23.20.116.56
ASN
14618
Organization
Amazon.com
City
Ashburn
Country
US

TLS certificate

Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Subject
webttt555.shop

DNS records

A
  • 23.20.116.56
NS
  • gracie.ns.cloudflare.com
  • charles.ns.cloudflare.com
SOA
Primary nameserver
charles.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418426599
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
23.20.116.56
IP version
4

Subdomains

Count
1
Subdomains
  • www.wedks.com

Registration record

Registrar
Gname.com Pte. Ltd.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • charles.ns.cloudflare.com
  • gracie.ns.cloudflare.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "wedks.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.83",
            "host": "charles.ns.cloudflare.com"
        },
        {
            "ip": "108.162.194.144",
            "host": "gracie.ns.cloudflare.com"
        }
    ],
    "zone": "wedks.com"
}
Location
{
    "ip": "23.20.116.56",
    "asn": "14618",
    "org": "Amazon.com",
    "city": "Ashburn",
    "country": "US"
}
Ssl
{
    "issuer": "Sectigo Limited / Sectigo Public Server Authentication CA DV R36",
    "subject": "webttt555.shop"
}
DNS records
{
    "A": [
        "23.20.116.56"
    ],
    "NS": [
        "gracie.ns.cloudflare.com",
        "charles.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"charles.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418426599, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "23.20.116.56",
    "family": 4
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.wedks.com"
    ]
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2025-11-03T04:34:59Z",
    "updated": "2026-10-24T16:30:56Z",
    "expires": "2027-11-03T04:34:59Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "charles.ns.cloudflare.com",
        "gracie.ns.cloudflare.com"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded
StateStored capture
Position1 / 10
Open capture Wayback Download
All capture links and hashes (10)
wedks.com: caution — 12/92 VirusTotal engines. PhishDestroy risk score 93/100 (critical).
Social preview card wedks.com: caution — 12/92 VirusTotal engines. PhishDestroy risk score 93/100 (critical). v 419b7b6e4848

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 93 report ↗
IP Reputation United States23.20.116.56 abuse score 0/100 0 reports checked Oct 26, 2026
Registrar Gname SG(SG)
Abuse contactcomplaint@gname.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wedks.com →
Hosting abuse contact complaint@gname.com Amazon.com · AS14618
RegistrationCreated Nov 3, 2025 (362d) — Expires Nov 3, 2027
WHOIS statusclientTransferProhibited
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 93/100
Submitted URLhttp://wedks.com/
Favicon Hash
Case ID
Observed page title
WEBUCCC
TLS Certificate
Issued by Sectigo Limited / Sectigo Public Server Authentication CA DV R36 · stored validity ends in 134 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States23.20.116.56
Network ASN
AS14618
AS name
AMAZON-AES - Amazon.com, Inc., US
Organization
Amazon.com
Observed location
United StatesAshburn, US
Server header
nginx

Nameservers 2

  • charles.ns.cloudflare.com
  • gracie.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Valid from
2026-08-28 00:00:00
Valid until
2027-03-14 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintfd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775
Certificate names · 2 SANs
  • webttt555.shop
  • www.webttt555.shop

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

viewdns.info · 23.20.116.56rapiddns.io

Latest Classified Outcome 2026-10-31 22:20:09 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-10-31 23:04:47 UTC
RDAP registration
Observed timeline last reachable: 2026-10-29 23:01:59 UTC last content: 2026-10-29 23:01:59 UTC current episode first observed: 2026-10-30 21:35:15 UTC observed RIP window: 2026-10-29 23:01:59 UTC → 2026-10-30 21:35:15 UTC · 22.55h midpoint estimate ≈ 2026-10-30 10:18:37 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.wedks.comDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 12 detections
alphaMountain.ai
CRDF
CyRadar
Emsisoft
Fortinet
G-Data
Gridinsoft
Kaspersky
MalwareURL
Netcraft
Sophos
Webroot
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://wedks.com/
WEBULL
Response
HTTP 200
HTML body
1,016 B
Compressed
578 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
1016
Content-Type
text/html; charset=utf-8
Date
Mon, 26 Oct 2026 11:41:24 GMT
Etag
"6adec40f-3f8"
Last-Modified
Mon, 26 Oct 2026 03:07:59 GMT
Server
nginx

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

Archived
Registration & observation details9

Availability observations

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

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

Captured network requests

Network requests: 7 SHA-256 hashes: 7 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:56 UTC.

Open this scan on URLScan 01a17812-6bf6-77b8-8105-7a815941c0ad ↗

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

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations28

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. 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-11-01 00:04:47.000000
    Evidence SHA-256
    820b3454a79f894e67b04c7614cceb6eeabf018c0b6fd03703606d954e752802
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 00:04:47
    Evidence reason
    unavailable
  2. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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 23:20:09.600237
    Evidence SHA-256
    d67f17873ab6334771d07dd3b9a9e8bfa490108372ed2f506a6eee3a33b36baa
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
  3. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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 23:20:09.600237
    Evidence SHA-256
    d67f17873ab6334771d07dd3b9a9e8bfa490108372ed2f506a6eee3a33b36baa
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
  4. 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-31 12:05:06.000000
    Evidence SHA-256
    3b332075b8c10d22c2363177e9ecddaa1f0dec4c6eb6745a7fdf90db0bff2e21
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 12:05:06
    Evidence reason
    unavailable
  5. 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-31 03:25:52.000000
    Evidence SHA-256
    811998d74c49e402d80e67d1154943e1aca6dbfac5b475d3ceb0c57ccacd592d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:25:52
    Evidence reason
    unavailable
  6. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-30 22:35:15.875079
    Evidence SHA-256
    8be630eb9a84e806aba7083927916d9e4d8d4ab0f0eb458cbced6d0f1846248f
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
  7. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    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-30 22:35:15.875079
    Evidence SHA-256
    8be630eb9a84e806aba7083927916d9e4d8d4ab0f0eb458cbced6d0f1846248f
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
  8. current_http_probeunknown
    Observation source
    current_http_probe
    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 12:01:28.000000
    Evidence SHA-256
    9bbb6192b6c906091d26e89635e48c8f70318750a37b065d0afd8f72d186c998
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:01:28
    Evidence reason
    unavailable
  9. 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-30 12:01:28.000000
    Evidence SHA-256
    9bbb6192b6c906091d26e89635e48c8f70318750a37b065d0afd8f72d186c998
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:01:28
    Evidence reason
    unavailable
  10. 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:01:59.000000
    Evidence SHA-256
    5e11dc830ef18f9a0f4cf4115f1051ff7cd07ee123ac24dc5f816e16584a8889
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:01:59
    Evidence reason
    alive_content
  11. 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:01:59.000000
    Evidence SHA-256
    5e11dc830ef18f9a0f4cf4115f1051ff7cd07ee123ac24dc5f816e16584a8889
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:01:59
    Evidence reason
    alive_content
  12. 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-29 17:14:29.775349
    Evidence SHA-256
    db74fcc6d756cb36943e7c7745a6a8737aaa6959c4a9679405e4f75391d96929
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 17:14:29.775349
    Evidence reason
  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:02:19.000000
    Evidence SHA-256
    f10b2d2b314c3469db930c3b9cf639559555d2aec1a3cbe483420d4245b45934
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:02:19
    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:02:19.000000
    Evidence SHA-256
    f10b2d2b314c3469db930c3b9cf639559555d2aec1a3cbe483420d4245b45934
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:02:19
    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 01:01:50.000000
    Evidence SHA-256
    da6285efb0440ea3a8b085ab861e1f758ae90a42aebd3463bc35fda1592fc286
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:01:50
    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 01:01:50.000000
    Evidence SHA-256
    da6285efb0440ea3a8b085ab861e1f758ae90a42aebd3463bc35fda1592fc286
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:01:50
    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 13:09:18.000000
    Evidence SHA-256
    454fcd256c8f84ada4f7f329d1c2c5018f1fa527fd44024ef3e652eece077151
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:09:18
    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 13:09:18.000000
    Evidence SHA-256
    454fcd256c8f84ada4f7f329d1c2c5018f1fa527fd44024ef3e652eece077151
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:09:18
    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 01:11:27.000000
    Evidence SHA-256
    39b942fef4b5395e36f3487c43efb35d5f30c0f521e8f41059108bc5b8ce4375
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:11:27
    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 01:11:27.000000
    Evidence SHA-256
    39b942fef4b5395e36f3487c43efb35d5f30c0f521e8f41059108bc5b8ce4375
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:11:27
    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 13:09:09.000000
    Evidence SHA-256
    01efbd3d8fa7d090beda3d6369c6de6ae96b1153bf5e2d98765aaa09f90e10d4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 13:09:09
    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 13:09:09.000000
    Evidence SHA-256
    01efbd3d8fa7d090beda3d6369c6de6ae96b1153bf5e2d98765aaa09f90e10d4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 13:09:09
    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 05:02:19.000000
    Evidence SHA-256
    adbd2c12557f7331e3b08a8418cb06035614cbd6f67a486437273ee779a2cbf8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 05:02:19
    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 05:02:19.000000
    Evidence SHA-256
    adbd2c12557f7331e3b08a8418cb06035614cbd6f67a486437273ee779a2cbf8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 05:02:19
    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-26 12:58:54.000000
    Evidence SHA-256
    5f7ad316c3306e5b5d859f4256a9dee57ef1e1506e1816854aee73049e27a426
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 12:58:54
    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-26 12:58:54.000000
    Evidence SHA-256
    5f7ad316c3306e5b5d859f4256a9dee57ef1e1506e1816854aee73049e27a426
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 12:58:54
    Evidence reason
  28. 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-26 12:43:44.156225
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · recorded

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
    wedks.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 93
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 12/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as phishing, Security threats
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Gname.com Pte. Ltd.. Abuse contacts: 1.
    • complaint@gname.com
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

6 entries
  1. Abuse report sent

    PD-20261026-C794F3 · Receipt 83441

    complaint@gname.com
  2. URLScan

    Page captured

    View source
  3. AlienVault OTX

    1 community references

    View source
  4. Cloudflare Radar

    Phishing

    View source
  5. Added to PhishDestroy

    wedks.com

    View source
  6. VirusTotal

    12/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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

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

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

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

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

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

Check for cloaking

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

wedks.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery Report stored SSL Labs Certificate hostname mismatch CF Radar Malicious OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-C794F3 Recipient: complaint@gname.com
PDF notice generated Notice text archived (317 characters)
Abuse notice text as sent to the provider 
Registrar: Gname.com Pte. Ltd. (Singapore)
Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain
Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
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?

6 evidence signal groups linked 1 stored notification records Unverified
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 wedks.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/wedks.com"
  title="PhishDestroy threat report for wedks.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>