Skip to security report
Analytics Dashboard
Domain security and threat intelligence
3933.pw favicon

3933.pw

In short

3933.pw is a phishing page detected by PhishDestroy on 2026-07-27. Risk: critical (86/100). Registrar: NameMart. Status: Content unavailable. VirusTotal: 12/89 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Registrar
NameMart
Registered
Jun 23, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 12/89 Spamhaus DBL: DBL_PHISH
OTX: 2 refs Jul 27, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
12 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
2
community references
Domain age
121 days
Source evidenceVirusTotal 12 / 89 · OTX 2 references 5 sources

VirusTotal

12 / 89 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
12 / 89
OTX
2 community refs
Source results Registration record

PhishDestroy threat report

Overview

3933.pw is a short, numeric .pw domain on the PhishDestroy blocklist. It does not present any known brand name. PhishDestroy first saw it on 2026-07-27. The site went offline on 2026-09-13, and on 2026-10-19 it was still dead with no active DNS. It no longer resolves for anyone who follows a link to it.

How the scam works

PhishDestroy has not assigned this domain to a specific scheme, so we cannot name a kit, brand or target. The independent verdicts point toward phishing. Spamhaus places it in its phishing category, and several antivirus and URL-reputation vendors flag it as malicious. Domains in this category typically serve pages that capture logins, personal details or payment information, then pass them to the operator. Anyone who reached the site while it was live should treat whatever they typed or approved there as exposed.

Evidence

On 2026-09-13, 12 of 89 VirusTotal engines flagged the domain. This is a minority, but the detections came from established vendors including BitDefender, ESET, Fortinet, G-Data, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam project Chong Lua Dao. Spamhaus DBL lists it under DBL_PHISH, a separate verdict reached independently of the antivirus engines. It also appears in two AlienVault OTX threat pulses, so other researchers have tied it to tracked malicious activity.

Infrastructure

The numeric name on the low-cost .pw extension gives a victim nothing recognizable to check against a real service. Throwaway names like this are cheap to register and easy to drop. The site went offline on 2026-09-13, the same day as the VirusTotal check. Its DNS is now inactive, which leaves the domain idle but open to reactivation.

What to do

If you entered a password on this site, change it there and on every account that reuses it, and turn on two-factor authentication. If you gave card or banking details, contact your bank and watch your statements for charges you do not recognize. Be wary of follow-up emails or messages that refer to the site. Defenders should keep 3933.pw blocked at DNS and proxy level. Check logs for lookups between 2026-07-27 and 2026-09-13 to find users who may have been exposed. Keep monitoring the domain in case it resolves again.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

Cloudflare Radar · 2026-09-13T00:26:14Z

Observed: · Retrieved:

Uuid
ef6936ee-c488-4ef0-aed5-72533c109625
VirusTotal · 2026-10-21T14:27:02Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 11,
    "suspicious": 2,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Cisco Umbrella": 924304
}
Registrar
NameMart Pte. Ltd.
Created
2026-06-23T10:33:05Z
Expires
2027-06-23T10:33:05Z
Updated
2026-07-10T06:54:18Z
First seen
2024-07-18T06:30:44Z
DNS records
[
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "support.namens.net",
        "value": "ns1.domainnamedns.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "19.200.14.109"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns3.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns4.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.domainnamedns.com"
    }
]
Dns at
2026-07-08T14:41:13Z
Jarm
3fd3fd0003fd3fd00042d43d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "0000.vc",
        "1023.pw",
        "10700.tw",
        "19268.vip",
        "21973.win",
        "2951.win",
        "32527.co",
        "3363.pw",
        "3539.win",
        "38017.org"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5bc61bf7c3b55154d931580b0211d96eb75",
    "sha256": "5b45226a4d68e5e5d424d6545c72f352758a2d1a9c6e8d29483827894dfed544",
    "subject": "43066.vip",
    "valid_to": "2026-09-21T19:12:46Z",
    "valid_from": "2026-06-23T19:12:47Z"
}
Registration record
{
    "registrar": "NameMart Pte. Ltd.",
    "registrar_iana_id": "4162",
    "registrar_url": "https://www.namemart.com",
    "created": "2026-06-23T10:33:05Z",
    "updated": "2026-07-10T06:54:18Z",
    "expires": "2027-06-23T10:33:05Z",
    "status": [
        "clientHold",
        "serverHold"
    ],
    "nameservers": [
        "ns1.domainnamedns.com",
        "ns2.domainnamedns.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client hold",
        "server hold"
    ],
    "events": {
        "registration": "2026-06-23T10:33:05Z",
        "registrar expiration": "2027-06-23T10:33:05Z",
        "last update of RDAP database": "2026-07-10T14:54:19Z"
    }
}

Questions about 3933.pw

Is 3933.pw legit?

No. PhishDestroy classifies 3933.pw as a phishing page (risk: critical, 86/100); it was first detected on 2026-07-27. VirusTotal: 12/89 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is 3933.pw safe to connect a wallet?

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

What should I do if I used 3933.pw?

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

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
OTX tags 2026-07all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar NameMart SE(SE)
Abuse contact["abuse@namemart.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for 3933.pw →
RegistrationCreated Jun 23, 2026 (121d) — Expires Jun 23, 2027
Time to First Unavailability 48 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJul 27, 2026

Network & certificates

Stored technical evidence

Network & DNS

Nameservers 2

  • ns1.domainnamedns.com
  • ns2.domainnamedns.com

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-06-23 19:12:47
Valid until
2026-09-21 19:12:46
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint5b45226a4d68e5e5d424d6545c72f352758a2d1a9c6e8d29483827894dfed544
Certificate names · 10 SANs
  • 0000.vc
  • 1023.pw
  • 10700.tw
  • 19268.vip
  • 21973.win
  • 2951.win
  • 32527.co
  • 3363.pw
  • 3539.win
  • 38017.org

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

Latest Classified Outcome 2026-10-21 14:53:36 UTC

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 Unknown Probe Inconclusive 20% 2026-10-21 01:00:28 UTC
RDAP registration Unknown
Observed timeline current episode first observed: 2026-09-30 16:14:55 UTC first terminal observation: 2026-09-30 16:14:55 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

12 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Fortinet
G-Data
Lionic
PhishFort
SOCRadar
VIPRE
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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

Stored observation history12

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

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    12/89 engine detections

    View source
  4. Added to PhishDestroy

    3933.pw

    View source

Community intelligence

1 community report

CategoryIMPERSONATION

Brand abuse: impersonation, fake affiliation, gambling, impersonating Las Vegas Sands Corp

Check for cloaking

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

3933.pw

Evidence & External Reports

Security Analysis
VirusTotal 12 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 2 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for 3933.pw · category: Impersonation · source checked
Flagged by automated brand-abuse detection on Jul 8, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
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?

2 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

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

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