Skip to security report
Analytics Dashboard
Domain security report
allocation-upsh.com favicon

allocation-upsh.com

“Upshift • UPSH Allocation”

Threat verdict
CriticalDomain Appeal
Assessment sources

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

Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
Spamhaus DBL: DBL_SPAM Stored blocklist matches: 2 Automated brand label: Discord Young domain: 2 days old Last known active
OTX: 4 refs Oct 16, 2026 Discord CDN
API
Registrar
NiceNIC
Resolved IP
188.114.97.3
Registered
Oct 14, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
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

Spamhaus DBL
DBL_SPAM
OTX references
4 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Let's Encrypt / YE1 · Hostname coverage not recorded
Age
2d Brand New!
Observed status
Reachable · access restricted 403
PhishDestroy
DestroyList
Listed

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.

Spamhaus DBL

DBL_SPAM

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.

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.

Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Evidence Summary

Critical
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

allocation-upsh.com was listed on the MetaMask external blocklist as of 2026-10-16, providing a dated reference for its presence in security monitoring sources. The domain also appeared in other security records on the same date, offering a broader context for its recorded network profile.

Recorded Evidence

On 2026-10-16, allocation-upsh.com was included in both the MetaMask and SEAL external blocklists. OTX documented four pulses for the domain on the same date. VirusTotal checked allocation-upsh.com on 2026-10-16, recording 0 detections from 92 total scanners. PhishDestroy internally listed the domain as of 2026-10-16. The domain was registered with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-10-14, and its SSL certificate was issued by Let's Encrypt / YE1, as scanned on 2026-10-16.

Interpretation

PhishDestroy contains an internal listing for allocation-upsh.com, which documents its inclusion in a curated security database. VirusTotal provides a scan record that measures how many detection engines observed the domain at a specific time. These sources, along with the MetaMask and SEAL blocklist entries, offer distinct types of security intelligence that can be compared over time.

Recommended Actions

For allocation-upsh.com, retain the MetaMask and SEAL blocklist records for ongoing reference. Preserve the VirusTotal scan results and OTX pulse history to support future monitoring and comparison with new security intelligence.

Data coverage & collection

20 · datasets with records / 11 · 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
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
DBL_SPAM
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
188.114.97.3 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE1
Page captures
3 · retained captures
HTML archives
1 · retained responses
Page analysis
5 · automated brand labels
Observed indicators
1 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
78/100 · mobile performance
Availability history
4 · stored state changes
Source observation history
2 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

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

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

Observed indicators

0 wallet · 1 Telegram

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

Telegram
https://t.me/upshiftfiStored page reference

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

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

NICENIC INTERNATIONAL GROUP CO., LIMITED · 188.114.97.3 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NiceNIC RU(RU) PhishDestroy Investigation
Abuse contactabuse@nicenic.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for allocation-upsh.com →
RegistrationCreated Oct 14, 2026 (2d · Brand New!) — Expires Oct 14, 2027
HTTP Status403 Forbidden
Elapsed Since First Report 20h
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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 DetectedOct 16, 2026
DOM Analysisanalyzed Oct 16, 2026score 90/1005 brand signals
IoC Extractionscanned Oct 17, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://allocation-upsh.com/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • cameron.ns.cloudflare.com
  • zoe.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-14 19:43:41
Valid until
2027-01-12 19:43:40
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6e118bdfb4e5ae2b0eb31af5fc3577baac95f82a937ab514fed5ca147c825f39

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

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-17 10:57:30 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Resolved Registration: Active
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-17 10:57:30 UTC
RDAP registration Active NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765 RDAP HTTP 200 source: Rdap Status Collector clientDeleteProhibitedclientTransferProhibited expires 2027-10-14 20:39:35 UTC checked 2026-10-17 04:32:19 UTC
Observed timeline last reachable: 2026-10-17 02:41:09 UTC last content: 2026-10-17 02:41:09 UTC current episode first observed: 2026-10-17 10:57:30 UTC observed RIP window: 2026-10-17 02:41:09 UTC → 2026-10-17 10:57:30 UTC · 8.27h midpoint estimate ≈ 2026-10-17 06:49:19 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of allocation-upsh.com · checked Oct 16, 2026

78
Needs Work
Performance
FCP
1.52s
First Contentful Paint
LCP
1.52s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
962ms
Total Blocking Time
SI
1.52s
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://allocation-upsh.com/
Final URL: https://allocation-upsh.com/
Upshift • UPSH Allocation
Check your indicative UPSH allocation from the Upshift points snapshot. Address lookup only: no wallet connection or signature required.
Response
HTTP 200
HTML body
25.0 KB
Compressed
7.8 KB
Links
2 internal · 14 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Content-Type-OptionsX-XSS-Protection
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Upshift • UPSH Allocation
Open Graph description: Check your indicative UPSH allocation by wallet address.
Twitter card: summary
Saved response-header values · 19
alt-svc
h3=":443"; ma=86400
cast-mode
default
cf-cache-status
DYNAMIC
CF-RAY
a4b7b79f0a6c590b-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors http: https:
Content-Type
text/html
Date
Fri, 16 Oct 2026 14:22:43 GMT
Last-Modified
Wed, 14 Oct 2026 22:49:08 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=fiSNwpyWJS9bJ7uZUzytg0dPMTK7LjfW4FE%2FPY1SNKeFyEqU1%2B%2BuXByZnWLO0neoz%2BCMfYm08Gr1td5iy5EWq60eFDUG1%2BnsRhlE4sGhotbLKjE%2BTAyo88GhwkmEbF35369
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
accept-encoding
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block

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

Archived
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:22:44 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:22:44 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:22:44 UTC
Source
legacy scan archive

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

Registration & observation details16

Registration evidence

RDAP statuses
clientdeleteprohibited · clienttransferprohibited
RDAP response
200
Registrar in registration evidence
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registrar IANA ID
3765
Expiration recorded by RDAP
Registration observation
Registration source
rdap_status_collector

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
8.27
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.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

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
Server header seen by scanner
cloudflare
Capture routing
Local archived 2026-10-16 14:22:44 UTC

Scanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_direct; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Provider response during scan: cloudflare_phishing_interstitial

Title shown to the security scannerSuspected Phishing | Cloudflare
Title shown to a browser visitorUpshift • UPSH Allocation
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

Collection history, report status and investigation channels

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. Domain Status Transition 2026-10-17 10:57:30 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-10-16 14:25:43 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
Stored observation history6

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

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    Reachable→Unavailable

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · First collection record

    Reachable

Earlier observations 1
  1. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
allocation-upsh.com detected and queued for full analysis
Oct 16, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
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.
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
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Discord
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Oct 16, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 403); the cause was not independently established.
Oct 17, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Oct 16, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Reachable · access restricted

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 allocation-upsh.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

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: allocation-upsh.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Upshift • UPSH Allocation”. Apparent target: Discord.

Stored VirusTotal result for allocation-upsh.com: 92 engines checked. Observed: 2026-10-16 17:28:52 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.

submit an appeal or review the FAQ page.

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/allocation-upsh.com"
  title="PhishDestroy threat report for allocation-upsh.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>