Skip to security report
Domain security report
w-across.cam favicon

w-across.cam

“Site Not Found”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Unverified Current reachability is unverified Observed · HTTP probe
Stored blocklist matches: 2 Automated brand label: Across Young domain: 2 days old
OTX: 4 refs Oct 16, 2026 Across 1 Report Sent CDN
API
Registrar
Dynadot
Resolved IP
199.36.158.100
Registered
Oct 14, 2026
2 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

OTX references
URLScan
URLScan
TLS Certificate
Hostname mismatch
Google Trust Services / WR3 · Certificate hostname mismatch
Age
2d Brand New!
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

VirusTotal

checked — no detections recorded

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: suspicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

High
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

w-across.cam was first observed on 2026-10-16, with a recorded entry on the MetaMask blocklist providing a dated reference for its security profile. The domain also appeared on SEAL's external blocklist, highlighting its presence in multiple security monitoring tools.

Recorded Evidence

VirusTotal checked w-across.cam on 2026-10-16, documenting 0 detections from 92 scanners. OTX referenced the domain in 4 pulses as of 2026-10-16. The domain was registered through Dynadot Inc on 2026-10-14, and PhishDestroy internally listed it. A PageSpeed performance score of 65 was recorded on 2026-10-16.

Interpretation

PhishDestroy contains an internal listing for w-across.cam, which documents its inclusion in a security database. VirusTotal records the domain’s scan results across numerous scanners, providing a technical assessment of its detection status. The evidence from OTX and external blocklists captures the domain’s visibility in threat intelligence sources, offering a broad context for review.

Recommended Actions

Preserve the MetaMask and SEAL blocklist entries for w-across.cam as reference points for future checks. Retain the VirusTotal scan results and OTX pulse references for ongoing comparison. Archive the PhishDestroy internal listing and PageSpeed performance score to support continued technical assessment.

Data coverage & collection

24 · datasets with records / 7 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
suspiciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Dynadot IncCollection time not recorded
Network & DNS
199.36.158.100 · 2 · nameserversCollection time not recorded
TLS certificate
Google Trust Services / WR3
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
9 · automated brand labels
Observed indicators
3 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
65/100 · mobile performance
Response records
1 · outgoing report records
Availability history
3 · stored state changes
Source observation history
1 · stored source events
Chainabuse records
1 · recorded reports
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 7

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
Download the dated observations and supporting metadata.
Extracted from stored page analysis

Observed indicators

2 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x078D782b760474a361dDA0AF3839290b0EF57AD6Format validated · Domain analysis
ETH
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913Format validated · Domain analysis
Telegram
https://t.me/acrosstgStored page reference

IoC extraction recorded 2026-10-17 04:00:27 UTC

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Dynadot Inc · 199.36.158.100 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationCreated Oct 14, 2026 (2d · Brand New!) — Expires Oct 14, 2027
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
DOM Analysisanalyzed Oct 16, 2026score 15/1009 brand signals
IoC Extractionscanned Oct 17, 20262 wallet · 1 Telegram IoCs
Submitted URLhttp://w-across.cam/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
199.36.158.100
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
Mountain View, US

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR3
Valid from
2026-10-16 06:44:30
Valid until
2027-01-14 07:42:50
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint94adcea787558ffbfbf08e99367e40965968acb0ba7711c7a587737ced7515e3
Certificate names · 99 SANs
  • 1inch.cam
  • 72wgsys.com
  • admin-dev.saude-brasil.com
  • admin-hml.saude-brasil.com
  • admin-service.gavergaraplaza.cl
  • admin.gastracker.top
  • admin.zylostechsolutions.com
  • aerodirome.finance
  • app.attentest.com
  • app.exactsafety.com.br
  • app.quadpro360.com
  • app.rentl.nicolei.games
  • azmy.best
  • backoffice-dev.prefilio.com
  • bebchat.bonnieleibel.com
  • behradazimi.dev
  • bellusto.com
  • bonnieleibel.com
  • bopz.online
  • bourbon.id.vn
  • bowleycompanyspellemporium.co.uk
  • brand.zylostechsolutions.com
  • brutostrail.com.br
  • calibrate.maxiluxsystems.com
  • cortex-rush.fun
  • dev.worki.sendu.co.il
  • disty4.com
  • djinga.fit
  • dmk-montage.nl
  • donan.bus-pass.jp
  • elitecservices.cl
  • eustaffgroup.eu
  • fit.leocolombini.com
  • forms.workfuse.com
  • gabrielleandmatthew828.com
  • games.zylostechsolutions.com
  • gddt.edutrack.pro.vn
  • gestao.taftup.com.br
  • gesy.es
  • ghostclear.com.br
  • grupoagp.dealerbi.com.br
  • gyodev.com
  • hackthon.mgsolutions.sbs
  • hood-warfare.com
  • inovegesso.com.br
  • intern.vitalbaeder-ulm.de
  • kreations.tech
  • kyberswap.cam
  • leawoodlawn.com
  • logly.at
  • maalon.in
  • nextlevelgamingevents.com
  • outliergroup.us
  • pablocasals.vortixcloud.com
  • pantheon.talk
  • pro.pharmamobile.net
  • puntoypalo.com
  • raizorweb.com.br
  • relayl.link
  • saintmen.com
  • sawtstudio.com
  • schools.zapelearning.com
  • staging.prefilio.com
  • starlgate.finance
  • sushistore.vn
  • taprobanetable.com
  • thebizwizard.pk
  • thewhiskybusiness.in
  • tools.northpath.nl
  • trailtheory.shaniara28.online
  • uralmedical.com
  • vision-vsc.com
  • voltz.pixoby.space
  • webfactur.com
  • worki.sendu.co.il
  • www.andbeyond.digital
  • www.behradazimi.dev
  • www.benditogabarito.com.br
  • www.bonnieleibel.com
  • www.bopz.online
  • www.bowleycompanyspellemporium.co.uk
  • www.brutostrail.com.br
  • www.classmixer.com
  • www.dmk-montage.nl
  • www.elitecservices.cl
  • www.ghostclear.com.br
  • www.hood-warfare.com
  • www.lemmaspor.dk
  • www.logly.at
  • www.melnat.com.mx
  • www.mshigienizacoes.com.br
  • www.nextlevelgamingevents.com
  • www.nset.eapteam.com
  • www.pandakarhu.com
  • www.puntoypalo.com
  • www.republika-wnetrz.pl
  • www.rubeniel.com.br
  • www.sanospark.com
  • zorvlex.com

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-16 20:21:29 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-17 10:00:12 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-16 14:27:15 UTC current episode first observed: 2026-10-16 20:21:29 UTC observed RIP window: 2026-10-16 14:27:15 UTC → 2026-10-16 20:21:29 UTC · 5.90h midpoint estimate ≈ 2026-10-16 17:24:22 UTC · precision high · 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.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of w-across.cam · checked Oct 16, 2026

65
Needs Work
Performance
FCP
5.6s
First Contentful Paint
LCP
5.66s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
43ms
Total Blocking Time
SI
5.6s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://w-across.cam/
Final URL: https://w-across.cam/
Across Protocol - Transfer Assets Between Layer 2s and Mainnet
Across is the bridge that just works. Bridge and swap tokens between any supported chain in seconds. Enjoy low fees, no custodial risk, and the reliability to handle any transfer size. Over $40B moved. No user funds lost.
Response
HTTP 200
HTML body
1.58 MB
Compressed
1,021.7 KB
Links
0 internal · 67 external
Detected technologies
vue
Selected response headers
Cache-Control: max-age=3600
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Across
Open Graph description: Across is the bridge that just works. Bridge and swap tokens between any supported chain in seconds.
Twitter card: summary_large_image
Saved response-header values · 16
Accept-Ranges
bytes
alt-svc
h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
Cache-Control
max-age=3600
Connection
keep-alive
Content-Encoding
gzip
Content-Length
1046245
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 14:34:17 GMT
Etag
"d9885e9a5853eefd2e5d32ac570a68626fbf2cbafc6b7296d2827f04701279b9"
Last-Modified
Mon, 12 Oct 2026 15:50:37 GMT
Strict-Transport-Security
max-age=31556926
Vary
x-fh-requested-host, accept-encoding
X-Cache
HIT
X-Cache-Hits
0
X-Served-By
cache-ber1080046-BER
X-Timer
S1792161257.310843,VS0,VE1

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

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-16 14:34:17 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 14:34:17 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-16 14:34:17 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details8

Availability observations

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

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Capture routing
Local archived 2026-10-16 14:34:17 UTC

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='w-across.cam', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-16 14:27:15 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 199.36.158.100.
Stored observation history4

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→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  4. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
w-across.cam detected and queued for full analysis
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Oct 16, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Oct 17, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 16, 2026
Brand Impersonation
Impersonation of Across
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 16, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Dynadot Inc, 2 abuse contacts
abuse@dynadot.comnetwork-abuse@google.com
Oct 16, 2026
DestroyList Published
Oct 16, 2026
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.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community intelligence

1 community report

CategoryPHISHING

Phishing clones of Across (w-across.cam) and 1inch (1inch.cam), both on Firebase Hosting and registered at Dynadot on 2026-10-14, load a hidden script that uses Base contract 0x623f65e5945c0fecf8f68ff9d98ce56fece6bc6a as its command server's address book. The script calls getData

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Community Scam Report — ChainAbuse
1 report filed for w-across.cam (1 written by a person) · category: Phishing · source checked
“Phishing clones of Across (w-across.cam) and 1inch (1inch.cam), both on Firebase Hosting and registered at Dynadot on 2026-10-14, load a hidden script that uses Base contract 0x623f65e5945c0fecf8f68ff9d98ce56fece6bc6a as its command server's address book. The script calls getData(), AES-decrypts a Cloudflare workers.dev URL, fingerprints the visitor, enumerates wallet extensions (it aborts on MetaMask Flask and Enkrypt), and injects remote JavaScript aimed at the visitor's wallet. Owner/creator”
— reported by Anonymous on Oct 16, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261016-DD91B4 Recipient: abuse@dynadot.com
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Unverified
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.

Official reporting routes
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 w-across.cam)
  • 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

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
Read the evidence in context

About This Report: w-across.cam

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Site Not Found”. Apparent target: Across.

Stored VirusTotal result for w-across.cam: 92 engines checked. Observed: 2026-10-16 15:32:24 UTC

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/w-across.cam"
  title="PhishDestroy threat report for w-across.cam"
  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>