Spamhaus DBL
phishing domain
wocsea.com is an OpenSea impersonation page detected by PhishDestroy on 2026-10-27.
“OpenSea”
PhishDestroy threat report
PhishDestroy’s intake on 2026-10-27 classified wocsea.com as malicious because the recorded page title was “OpenSea” and the page displayed a prompt asking users to enable JavaScript. The site returned HTTP 200 on that date, and the title and prompt were captured in the page fetch.
Impersonation pages copy the branding of a legitimate service such as OpenSea to lure visitors into trusting the site. Requiring JavaScript lets the page load hidden scripts that can capture login credentials, wallet connections, or redirect users to malicious destinations.
VirusTotal scanned the domain on 2026-10-27 and reported zero detections from 92 engines; Google Safe Browsing also showed no flag on that date. External blocklists MetaMask and SEAL listed the domain, and PhishDestroy’s internal list marked it as malicious. urlscan.io recorded a redirect chain from wocsea.com to wocsea.com and then to 911955.com, assigning a malicious score of 87 and tagging the page as suspicious; OTX noted four pulses referencing the domain.
The domain was registered with Gname.com Pte. Ltd. on 2026-05-07, 173 days before the first observation. DNS resolution on 2026-10-27 returned IP 103.82.212.167 in the RACKFLARELIMITED network in Hong Kong, and the TLS certificate from Let’s Encrypt (YR1) was valid from 2026-10-20 to 2027-01-18.
Visitors should avoid entering credentials, enabling JavaScript, or connecting wallets to wocsea.com; if credentials were submitted, change the associated passwords immediately. Defenders can block wocsea.com and its redirect target 911955.com, monitor DNS queries for the recorded IP and domain, and review logs for any connections to the observed host.
phishing domain
Malicious · engine verdict · score 87
SHA-256 c6c2455d194329668531ff51372fa2ea4f92f8bd8d7bfb9472205b7e79c33ffe
Observed: · Retrieved:
| Uuid | 01a17e38-16ba-763d-9be9-7744ed47900e |
|---|---|
| Final url | https://911955.com/ |
| Status | 200 |
| Redirected | off-domain |
| Redirects | [
{
"to": "https://wocsea.com/",
"from": "http://wocsea.com/",
"status": 307
},
{
"to": "https://911955.com/",
"from": "https://wocsea.com/"
}
] |
| Ip | 18.166.240.165 |
| Ptr | ec2-18-166-240-165.ap-east-1.compute.amazonaws.com |
| Contacted domains | [
"wocsea.com",
"app.chaport.com",
"assets.chaport.com"
] |
| Contacted IP addresses | [
"18.166.240.165",
"104.26.14.45",
"103.82.212.167"
] |
| Asns | [
"16509",
"13335",
"59371"
] |
| Countries | [
"HK"
] |
| Document hash | 792d7481b87e3a1e1080970a07be10ae61dfa7869d5898e5506fd24075badab0 |
| Tls | {
"san": [
"wocsea.com"
],
"cipher": "AES_256_GCM",
"issuer": "YR1",
"subject": "wocsea.com",
"protocol": "TLS 1.3",
"valid_to": "2027-01-18T10:33:35Z",
"valid_from": "2026-10-20T10:33:36Z"
} |
| Domain age days | 1351 |
| Apex age days | 1351 |
| Tls age days | 8 |
| Tls valid days | 89 |
| Requests | 18 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 87,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html",
"strict-transport-security": "max-age=31536000"
} |
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
0 / 92 engine detections · stored summary
Open reportObserved: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 0,
"suspicious": 0,
"undetected": 39
} |
|---|---|
| Reputation | 0 |
| Created | 2025-02-20T00:00:00Z |
| Updated | 2026-02-21T00:00:00Z |
| First seen | 2025-02-23T16:18:23Z |
| DNS records | [
{
"ttl": 600,
"type": "CNAME",
"value": "zyqdwe35.as66588.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "a.share-dns.com"
},
{
"ttl": 600,
"type": "SOA",
"rname": "master.share-dns.com",
"value": "a.share-dns.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "b.share-dns.net"
},
{
"ttl": 60,
"type": "CNAME",
"value": "xaeyrs6b.as66588.com"
},
{
"ttl": 60,
"type": "A",
"value": "66.203.148.87"
}
] |
| Dns at | 2026-10-27T16:18:12Z |
| Jarm | 29d29d00029d29d21c42d42d000000c1fc3d47ef34532079f4922fcb05ef65 |
| Certificate | {
"san": [
"wocsea.com"
],
"issuer": "Let's Encrypt / YR1",
"serial": "647339d8dcad37ca419843d9104d369fdfa",
"sha256": "82c797a6f0fb6fa2ee6d85dee4f6ca43221f04e6932742260429ff6eb48e7cfe",
"subject": "wocsea.com",
"valid_to": "2027-01-18T10:33:35Z",
"valid_from": "2026-10-20T10:33:36Z"
} |
| Registry data | {
"status": [
"client transfer prohibited"
],
"events": {
"expiration": "2028-05-07T18:43:07Z",
"registration": "2026-05-07T18:43:07Z",
"last update of RDAP database": "2026-10-14T10:06:09Z"
},
"registrar": "Gname.com Pte. Ltd.",
"registrar_iana_id": "1923"
} |
The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.
Scan report
Open report4 community references
Open reportprovider verdict: clean
Open reportObserved: · Retrieved:
| Uuid | 942770e8-7982-4fd1-a469-620bf2fe710d |
|---|---|
| Final url | https://911955.com/ |
| Status | 200 |
| History | [
{
"url": "https://wocsea.com/",
"status": 200
},
{
"url": "https://wocsea.com/pc/",
"status": 200
},
{
"url": "https://911955.com/",
"status": 200
}
] |
| DOM structure hash | 63099935bb99ef71c72845025185e2386e7f13b13d6c742b3e7e3c7adf1148a4 |
| Document hash | 792d7481b87e3a1e1080970a07be10ae61dfa7869d5898e5506fd24075badab0 |
| Domain risks | [
"Gambling",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "911955.com",
"type": "A",
"value": "18.166.240.165"
}
] |
| Dnssec valid | false |
| Ip | 127.0.1.12 |
| Registration record | {
"registrar": "Gname.com Pte. Ltd.",
"created": "2025-07-09T18:10:46Z",
"updated": "2026-07-11T06:37:28Z",
"expires": "2027-07-09T18:10:46Z",
"nameservers": [
"a4.share-dns.com",
"b4.share-dns.net"
]
} |
No threat flag
Open report80 / 100 · heuristic score · 2 brand references · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "wocsea.com"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Web archive observations | {
"last": "2026-10-27T16:39:44Z",
"first": "2026-05-08T18:56:35Z",
"changes": 2,
"days_archived": 4,
"scans_per_day": 0.02,
"avg_page_bytes": 1623
} |
| Page title and metadata | {
"title": "OpenSea",
"ogImage": "https://static.seadn.io/og/generic.jpg",
"ogTitle": "OpenSea, exchange everything — token trading and NFT marketplace",
"description": "OpenSea, exchange everything — token trading and NFT marketplace. Welcome to the best place to discover, trade, and create onchain.",
"twitterCard": "summary_large_image",
"ogDescription": "OpenSea, exchange everything — token trading and NFT marketplace. Welcome to the best place to discover, trade, and create onchain.",
"twitterCreator": "@opensea"
} |
| Trackers | {
"requests": 7
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 60,
"tls": 177,
"wait": 180,
"connect": 175,
"download": 0
},
"response_ms": 592
} |
| TLS connection | {
"alpn": "http/1.1",
"cipher": "TLS_AES_256_GCM_SHA384",
"protocol": "TLSv1.3",
"versions": [
"TLSv1",
"TLSv1.1",
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
80,
443
]
} |
| Carbon | {
"bytes": 2132,
"co2_grams": 0.0001,
"cleaner_than": 95
} |
| Location | {
"ip": "103.82.212.167",
"asn": "59371",
"org": "RACKFLARELIMITED",
"city": "Tai Chuen",
"country": "HK"
} |
| Ssl | {
"issuer": "Let's Encrypt / YR1",
"subject": "wocsea.com"
} |
| DNS records | {
"A": [
"103.82.212.167"
],
"CNAME": [
"zyqdwe35.as66588.com"
]
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"header": "max-age=31536000",
"message": "HSTS header does not include all subdomains."
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": false,
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": false,
"contentSecurityPolicy": false,
"strictTransportPolicy": "max-age=31536000",
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "103.82.212.167",
"family": 4
} |
| Redirects | {
"chain": [
"https://wocsea.com"
]
} |
| Registration record | {
"registrar": "Gname.com Pte. Ltd.",
"created": "2026-05-07T18:43:07Z",
"updated": "2026-09-09T10:06:01Z",
"expires": "2028-05-07T18:43:07Z",
"status": [
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"a11.share-dns.com",
"b11.share-dns.net"
]
} |
| HTTP headers | {
"headers": {
"server": "nginx",
"content-type": "text/html",
"strict-transport-security": "max-age=31536000"
}
} |
No. PhishDestroy classifies wocsea.com as an OpenSea impersonation page (risk: critical, 80/100); it was first detected on 2026-10-27. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on wocsea.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Checked, no match
Last checked
a.share-dns.coma11.share-dns.comb.share-dns.netb11.share-dns.netLocation describes the IP network.
82c797a6f0fb6fa2ee6d85dee4f6ca43221f04e6932742260429ff6eb48e7cfewocsea.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Google PageSpeed Insights — mobile performance audit of wocsea.com · checked Oct 27, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://wocsea.com/https://wocsea.com/Content-Type: text/htmlContent-Encoding: gzipServer: nginxsummary_large_imagequic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"keep-alivegziptext/htmlTue, 27 Oct 2026 16:41:17 GMTW/"6ad7e152-854"Tue, 20 Oct 2026 21:46:58 GMTnginxmax-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
live_content
content_served
Reachable
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.
Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
4 community references
View source0/92 engine detections
View sourcePD-20261027-411E6D · Receipt 83876
wocsea.com
View sourcePage captured
View sourceWe 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
38 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
wocsea.com PD-20261027-411E6D Recipient: complaint@gname.com 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)
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
Template-based draft • optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
wocsea.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.