Skip to security report
Domain security and threat intelligence
tordaily.com favicon

tordaily.com

In short

tordaily.com is a Dhl impersonation page detected by PhishDestroy on 2026-08-31. Risk: critical (88/100). Registrar: DNS Africa. Status: Last known active. Hosting: AS13335 Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.

“WetheNorth Market – Tor Daily”

Registrar
DNS Africa
Resolved IP
188.114.96.3
Registered
May 11, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 5/92 Automated brand label: Dhl
OTX: 5 refs Aug 31, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dns.business. The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260831-A5FDA8
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 5 / 92 · OTX 5 references 6 sources

VirusTotal

5 / 92 engine detections

Open report

URLQuery

checked — no detections recorded

Open report

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
5 / 92
OTX
5 community refs
Page captures
3

PhishDestroy threat report

Overview

tordaily.com presents itself as a Tor link guide under the heading "WetheNorth Market – Tor Daily". It uses the WeTheNorth Market name to draw in people searching for that market's access points. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-08-31. On 2026-10-19 the domain was still resolving and serving live content.

How the scam works

Sites like this rank for searches such as a market's name plus "link" or "mirror" and promise a verified way in. The visitor is sent to a lookalike login or deposit page that the operators control. Anything entered there can be captured, including usernames, passwords and account recovery details. If the clone also shows a wallet address for deposits, any cryptocurrency sent goes straight to the scammers and cannot be recovered. Because it borrows a familiar brand and a neutral "daily" news framing, the page looks like a reference resource rather than a trap.

Evidence

Independent detection is still thin. On 2026-10-14, 5 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. Most engines therefore still let it through, which is why a visitor's browser or antivirus may not warn them. The domain also appears in 5 AlienVault OTX threat pulses, so other researchers are tracking it too. Of the major blocklists, only PhishDestroy currently lists it.

Infrastructure

The domain was registered on 2025-05-11 through DNS Africa Ltd, more than fifteen months before PhishDestroy detected it. That long, quiet lifespan fits a site built to collect search traffic over time rather than a short burst campaign. It sits behind Cloudflare (AS13335) on a US-based address, so the real origin server is hidden from view.

What to do

If you entered a username or password on this site, change it at once on the genuine service and anywhere else you reused it. Turn on two-factor authentication, and treat any recovery phrases or PGP-related details you typed there as exposed. Do not send funds to any address this site displays. Crypto that has already been transferred cannot be reversed, so stop further payments and keep a record of the transaction details. Security teams should block tordaily.com at DNS and proxy level and add it to their phishing feeds, given how few engines catch it today.

Collected source details

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

URLScan · 2026-08-31T15:14:11Z

Observed: · Retrieved:

Uuid
01a05862-7b12-7364-854a-d726eb5d8c4e
Final url
https://tordaily.com/wethenorth-market/
Status
200
Redirects
[
    {
        "to": "https://tordaily.com/z0f76a1d14fd21a8fb5fd0d03e0fdc3d3cedae52f",
        "from": "https://tordaily.com/wethenorth-market/"
    },
    {
        "to": "https://tordaily.com/wethenorth-market/",
        "from": "https://tordaily.com/z0f76a1d14fd21a8fb5fd0d03e0fdc3d3cedae52f",
        "status": 302
    }
]
Ip
188.114.96.3
Contacted domains
[
    "s.w.org"
]
Contacted IP addresses
[
    "192.0.77.48",
    "188.114.96.3"
]
Asns
[
    "2635",
    "13335"
]
Countries
[
    "US"
]
Linked domains
[
    "www.youtube.com",
    "www.bitchute.com",
    "hn2paw7zaahbikbejiv6h22zwtijlam65y2c77xj2ypbilm2xs4bnbid.onion"
]
Social
[
    "https://www.youtube.com/@TorDaily"
]
Document hash
d8fd7eb52af16ceac24fdaad0e9ff7dc8685f22563e4df87fe9d9238f09f4a01
Script hashes
[
    "cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf",
    "5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89",
    "de8e8b77056034a96969eba8df35e32f2296c1ef44737c8f37f77fa8447a3900",
    "1f560c3e9fb5beeed86da7d5be1ae459c22af6ec1d58f77e2a89a20063ef7ba2",
    "d6c6d0b6440485f2536e96758b074c4713ef69a56511f2af2128f23ce6eebdca",
    "063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3"
]
Globals
[
    "jQuery",
    "sf_position",
    "sf_templates",
    "sf_input",
    "tie",
    "createTicker",
    "isInTag",
    "typetext",
    "tie_isMobile",
    "html5",
    "Modernizr",
    "yepnope",
    "browserPrefixes",
    "sf_addItem",
    "_wpemojiSettings",
    "$window",
    "$the_post",
    "$wrapper",
    "php_js",
    "window_height",
    "isActive",
    "twemoji",
    "wp"
]
Cookies
[
    "wssplashchk"
]
Storage keys
[
    "wpEmojiSettingsSupports"
]
Tls
{
    "san": [
        "tordaily.com",
        "*.tordaily.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "tordaily.com",
    "protocol": "QUIC",
    "valid_to": "2026-11-29T13:04:56Z",
    "valid_from": "2026-08-31T12:05:06Z"
}
Domain age days
2033
Apex age days
2033
Tls age days
0
Tls valid days
90
Requests
24
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 66,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "strict-transport-security": "max-age=0"
}
Cloudflare Radar · 2026-08-31T15:53:08Z

Observed: · Retrieved:

Uuid
fa19c369-d041-410b-945d-24e9a82dc97e
Final url
https://tordaily.com/
Status
200
History
[
    {
        "url": "https://tordaily.com/",
        "status": 200
    }
]
DOM structure hash
40af685a21561973069a31647c27a6f19581d2ef2f40098be02546c36ec9c322
Document hash
fd32a83c963e3cc04421411a93081356bea86ed272eee751e4e680fa248ae176
Domain risks
[
    "News & Media",
    "Entertainment"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "tordaily.com",
        "type": "A",
        "value": "172.67.172.238"
    },
    {
        "name": "tordaily.com",
        "type": "A",
        "value": "104.21.30.129"
    },
    {
        "name": "tordaily.com",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:acee"
    },
    {
        "name": "tordaily.com",
        "type": "AAAA",
        "value": "2606:4700:3036::6815:1e81"
    }
]
Dnssec valid
false
Ip
172.67.172.238
Registration record
{
    "registrar": "DNS Africa Ltd",
    "created": "2025-05-11T14:51:37Z",
    "updated": "2026-03-02T18:25:55Z",
    "expires": "2030-05-11T14:51:37Z",
    "nameservers": [
        "conrad.ns.cloudflare.com",
        "meadow.ns.cloudflare.com"
    ]
}

Questions about tordaily.com

Is tordaily.com legit?

No. PhishDestroy classifies tordaily.com as a Dhl impersonation page (risk: critical, 88/100); it was first detected on 2026-08-31. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.

Is tordaily.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on tordaily.com. 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 tordaily.com?

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

Stored Capture · 3 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar DNS Africa ZA(ZA)
Abuse contactabuse@dns.business
RegistrationCreated May 11, 2025 — Expires May 11, 2030
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
DOM Analysisanalyzed Oct 9, 2026score 88/1002 brand signals
Submitted URLhttps://tordaily.com/wethenorth-market/
Favicon Hash
Case ID
Observed page title
WetheNorth Market – Tor Daily
Automated brand references
Dhl Usps
TLS Certificate
Issued by Google Trust Services · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.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

  • conrad.ns.cloudflare.com
  • meadow.ns.cloudflare.com

Mail routing 1 MX record

  • _dc-mx.804dd62916c0.tordaily.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-08-31 12:05:06
Valid until
2026-11-29 13:04:56
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-10 22:02:52 UTC
Collection source
PhishDestroy collector
Certificate fingerprinteb26928e6982577c70970ee22f85bc15529548a18c820a829784fc3f98e65d83
Certificate names · 2 SANs
  • tordaily.com
  • *.tordaily.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-22 10:36:43 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 10:36:43 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:36:43 UTC last content: 2026-10-22 10:36:43 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.
Technologies · 10 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar

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 tordaily.com · checked Aug 31, 2026

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

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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.

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Browser
WetheNorth Market – Tor Daily
Crawler
Tor Daily
tordaily.com
Saved result
Keitaro TDS
Stored observation history24

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

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 19
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    protected→live_content

    content_served

  10. Availability monitor · Recorded state

    live_content→protected

    http_access_restricted · Cloudflare · access_restriction

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content

    content_served

  16. VirusTotal · Detection count

    3→5

  17. VirusTotal · Detection count

    2→3

  18. VirusTotal · Detection count

    0→2

  19. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. VirusTotal

    5/92 engine detections

    View source
  2. AlienVault OTX

    5 community references

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. Abuse report sent

    PD-20260831-A5FDA8

    abuse@dns.business
  5. Added to PhishDestroy

    tordaily.com

    View source
  6. URLScan

    Page captured

    View source

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260831-A5FDA8 Recipient: abuse@dns.business
Page title stored with report: WetheNorth Market – Tor Daily
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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 tordaily.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

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