Skip to security report
Domain security and threat intelligence
logistics-ups.online favicon

logistics-ups.online

“Bot Verification”

Registrar
DYNADOT
Resolved IP
172.67.167.228
Registered
Sep 2, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 7/90 Spamhaus DBL: DBL_SPAM Automated brand label: UPS Google Safe Browsing: threat flag recorded
OTX: 4 refs Sep 2, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 7. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 7 / 90 · Google Safe Browsing: flagged · OTX 4 references 7 sources

VirusTotal

7 / 90 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

DBL_SPAM

OTX

4 community references

Open report

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

Network Security Intelligence
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:

Analysis

Critical
VirusTotal
7 / 90
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

logistics-ups.online is a phishing site that impersonates UPS, the parcel carrier. It targets people expecting a package. PhishDestroy first flagged it on 2026-09-02, the same day the domain was registered. The site went offline on 2026-09-11, and it was still dead with no active DNS when checked on 2026-10-19.

How the scam works

Fake carrier sites like this one are usually reached through a text or email. The message claims a parcel is held, misaddressed or awaiting a small fee, and the link leads to a page dressed in UPS branding. That page asks for a name, address, phone number and often card details to "release" the delivery. Victims lose that personal and payment data, which is then used for card fraud or follow-up scams. The page title read "Bot Verification" rather than anything UPS-related, while urlscan.io detected UPS branding on the content, which is the basis of our impersonation classification.

Evidence

Several independent sources back the verdict. Google Safe Browsing lists the domain for social engineering, which triggers warnings in major browsers. urlscan.io rated it malicious and recognized UPS as the imitated brand. On VirusTotal, 7 of 90 engines flagged it as of 2026-09-04: alphaMountain.ai, CRDF, Fortinet, Gridinsoft, LevelBlue, SOCRadar and desenmascara.me. That is a modest count, but typical for a days-old domain. Spamhaus DBL lists it as a spam domain, and it appears in 4 AlienVault OTX threat pulses alongside the PhishDestroy blocklist.

Infrastructure

The domain was registered through DYNADOT LLC on 2026-09-02 and was caught that same day. It stayed up for only about nine days before going dark, a short lifespan that fits a disposable phishing domain. The keyword-stuffed name "logistics-ups" is built to look plausible in a text message. Traffic ran through Cloudflare, Inc. on an address geolocated to Canada, which hides the real origin server. The site carried a valid Google Trust Services certificate, so a browser padlock said nothing about whether it was safe.

What to do

If you entered card details on this page, call your bank to block the card and dispute any unfamiliar charges. If you shared your address, phone number or other personal details, expect targeted follow-up scams by text, email or phone. Never pay "redelivery" or "customs" fees through links in messages. Track parcels only by typing the carrier's official address yourself. Defenders should block the domain and look for SMS or email lures containing "logistics-ups" in mail and proxy logs.

Extracted from stored page analysis

Observed indicators

3 wallet · 1 Telegram

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

BTC
bc1q8tgtsq70uvcfz9a4yg804ls99rvhku3mgpg065Format validated · Domain analysis
ETH
0x3018d810aee5acc16321ef3b0507ccaafd9a31afFormat validated · Domain analysis
TRX
TGSc2CsD1r6McSagPSQgvNccFNC2k6CKPMFormat validated · Domain analysis
Telegram
https://t.me/americanmidlandlogisticsStored page reference

IoC extraction recorded 2026-09-03 04:00:14 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 2 captures

Observed page title
Bot Verification
Automated brand references
UPS
TLS Certificate
Issued by Google Trust Services / WE1

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Ups report ↗
Google Safe Browsing Flagged Social engineering checked Sep 11, 2026
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar DYNADOT US(US)
RegistrationCreated Sep 2, 2026 (48d · New) — Expires Sep 2, 2027
Time to First Unavailability 9 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 DetectedSep 2, 2026
IoC Extractionscanned Sep 3, 20263 wallet · 1 Telegram IoCs
Submitted URLhttps://logistics-ups.online/
Favicon Hash
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
172.67.167.228
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • jade.ns.cloudflare.com
  • tom.ns.cloudflare.com

Mail routing 1 MX record

  • _dc-mx.8716c30c827c.logistics-ups.onlinepriority 0

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-02 08:00:38
Valid until
2026-12-01 08:58:10
Validity
Within stored validity dates
Collection time
2026-09-02 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint20f5b8dfb13d7b84f2c26a6f71332bd9befd752ca31868c0ca89b9b49809255e

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-19 08:21:20 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-19 01:13:33 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-02 22:16:21 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-02 22:16:21 UTC → 2026-09-30 16:14:55 UTC · 665.98h midpoint estimate ≈ 2026-09-16 19:15:38 UTC · precision low · 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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 90 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
CRDF
Fortinet
Gridinsoft
LevelBlue
SOCRadar
desenmascara.me
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of logistics-ups.online · checked Sep 2, 2026

98
Good
Performance
FCP
1.83s
First Contentful Paint
LCP
1.98s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

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

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

Check for cloaking

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

logistics-ups.online
Saved result
Unreachable
Stored observation history17

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 12
  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

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. VirusTotal · Detection count

    6→7

  8. VirusTotal · Detection count

    5→6

  9. VirusTotal · Detection count

    4→5

  10. VirusTotal · Detection count

    1→4

  11. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  12. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    7/90 engine detections

    View source
  4. Added to PhishDestroy

    logistics-ups.online

    View source
  5. URLScan

    Page captured

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

5 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.

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 logistics-ups.online)
  • 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
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.

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/logistics-ups.online"
  title="PhishDestroy threat report for logistics-ups.online"
  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>