Skip to security report
Analytics Dashboard
Domain security and threat intelligence
dalekane.blog favicon

dalekane.blog

In short

dalekane.blog is a blocklisted domain detected by PhishDestroy on 2026-10-25. Risk: critical (86/100). Registrar: Spaceship. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 3/92 engines flag it. Do not enter credentials or connect a wallet.

“18+ Access”

Review the evidence
Registrar
Spaceship
Resolved IP
104.21.79.89
Registered
Oct 18, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 3/92 Young domain: 7 days old
VirusTotal
3 / 92
engine detections
OTX
3
community references
Cloudflare Radar
suspicious
source verdict
Page captures
3
open gallery
Domain age
7 days
Reports sent
—
No sent record
OTX: 3 refs Oct 25, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 3. Exercise extreme caution — do not enter credentials or personal information.
Source evidenceVirusTotal 3 / 92 · OTX 3 references 5 sources

VirusTotal

3 / 92 engine detections

Open report
VirusTotal · 2026-10-19T10:10:41Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
}
Registrar
Spaceship, Inc.
Created
2026-10-18T06:32:59Z
Expires
2027-10-18T06:32:59Z
Updated
2026-10-18T06:47:10Z
First seen
2026-10-18T07:12:49Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::6815:4f59"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:a96d"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "adrian.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.169.109"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.79.89"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ivan.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "adrian.ns.cloudflare.com"
    }
]
Dns at
2026-10-19T10:15:56Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.dalekane.blog",
        "dalekane.blog"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "686e10874e6b0bfc241b2cecce69d788d34",
    "sha256": "7c1bc4140aa27c5e0ea50aaa9de89ab911ee9424f26f2d59ff3fd2615be65140",
    "subject": "dalekane.blog",
    "valid_to": "2027-01-16T05:55:21Z",
    "valid_from": "2026-10-18T05:55:22Z"
}
Registration record
{
    "registrar": "Spaceship, Inc.",
    "registrar_iana_id": "3862",
    "registrar_url": "https://www.spaceship.com/",
    "created": "2026-10-18T06:32:59Z",
    "updated": "2026-10-18T06:47:10Z",
    "expires": "2027-10-18T06:32:59Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "adrian.ns.cloudflare.com",
        "ivan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "server transfer prohibited",
        "add period"
    ],
    "events": {
        "last changed": "2026-10-18T06:47:10Z",
        "registration": "2026-10-18T06:32:59Z",
        "registrar expiration": "2027-10-18T06:32:59Z",
        "last update of RDAP database": "2026-10-18T07:12:41Z"
    }
}

Cloudflare Radar

Suspicious

Not recorded
Open report
Cloudflare Radar · 2026-10-25T04:12:39Z

Observed: · Retrieved:

Uuid
1ab6811b-2794-4224-bde1-8c121cce294f
Final url
https://dalekane.blog/
Status
200
History
[
    {
        "url": "https://dalekane.blog/",
        "status": 200
    }
]
DOM structure hash
46371e6b3e4d3ae4cfb910ba652c3616537fb432622629e15672f22a5cffc417
Document hash
3f2b0efcf7a89da27961ee353d3ec25a6f53a6bdc72c4cdb014ce50e4634eced
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "dalekane.blog",
        "type": "A",
        "value": "172.67.169.109"
    },
    {
        "name": "dalekane.blog",
        "type": "A",
        "value": "104.21.79.89"
    },
    {
        "name": "dalekane.blog",
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:a96d"
    },
    {
        "name": "dalekane.blog",
        "type": "AAAA",
        "value": "2606:4700:3036::6815:4f59"
    }
]
Dnssec valid
false
Ip
172.67.169.109
Registration record
{
    "registrar": "Spaceship, Inc.",
    "created": "2026-10-18T06:32:59Z",
    "updated": "2026-10-23T06:35:23Z",
    "expires": "2027-10-18T06:32:59Z",
    "nameservers": [
        "adrian.ns.cloudflare.com",
        "ivan.ns.cloudflare.com"
    ]
}

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Not recorded
Open report
URLScan · 2026-10-19T09:00:42Z

Observed: · Retrieved:

Uuid
01a15364-2ba6-7339-8707-da647f76dfe7
Final url
https://dalekane.blog/
Status
200
Ip
172.67.169.109
Contacted IP addresses
[
    "172.67.169.109"
]
Asns
[
    "13335"
]
Linked domains
[
    "google.com"
]
Document hash
37c488d23f322f4172e4457e29d0f371ed7fffef0c855dfb47d5ec14e3d29ab8
Script hashes
[
    "52fd3bb33a07f0fd1f2b93a56ad4004af8e8db362d501b469aee5728c6058f1d"
]
Globals
[
    "lang",
    "rtlLanguages",
    "i18n",
    "t",
    "tt",
    "go"
]
Cookies
[
    "gate_time"
]
Tls
{
    "san": [
        "*.dalekane.blog",
        "dalekane.blog"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "dalekane.blog",
    "protocol": "QUIC",
    "valid_to": "2027-01-16T05:55:21Z",
    "valid_from": "2026-10-18T05:55:22Z"
}
Domain age days
0
Apex age days
0
Tls age days
1
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 84,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}

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

Collected source details

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

Every stored field, with its source and date
Website checks · 2026-10-25T04:14:56Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "dalekane.blog"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Trackers
{
    "requests": 3
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.193.120",
            "host": "ivan.ns.cloudflare.com"
        },
        {
            "ip": "172.64.32.57",
            "host": "adrian.ns.cloudflare.com"
        }
    ],
    "zone": "dalekane.blog"
}
Location
{
    "ip": "2606:4700:3034::ac43:a96d",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "dalekane.blog"
}
DNS records
{
    "A": [
        "172.67.169.109",
        "104.21.79.89"
    ],
    "NS": [
        "ivan.ns.cloudflare.com",
        "adrian.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"adrian.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417891626, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3034::ac43:a96d",
        "2606:4700:3036::6815:4f59"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3034::ac43:a96d",
    "family": 6
}
Registration record
{
    "registrar": "Spaceship, Inc.",
    "created": "2026-10-18T06:32:59Z",
    "updated": "2026-10-23T06:35:23Z",
    "expires": "2027-10-18T06:32:59Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp",
        "serverTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "adrian.ns.cloudflare.com",
        "ivan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about dalekane.blog

Is dalekane.blog legit?

No. PhishDestroy classifies dalekane.blog as a blocklisted domain (risk: critical, 86/100); it was first detected on 2026-10-25. VirusTotal: 3/92 engines flag it. Treat the site as unsafe.

Is dalekane.blog safe to connect a wallet?

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

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

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://dalekane.blog/
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
Observed page title
18+ Access
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 82 days

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-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
Abuse contact["abuse@spaceship.com", "06e9e0e26edd1e63s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for dalekane.blog →
RegistrationCreated Oct 18, 2026 (7d · Very New!) — Expires Oct 18, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 86/100
Submitted URLhttp://dalekane.blog/
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.79.89
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adrian.ns.cloudflare.com
  • ivan.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-18 05:55:22
Valid until
2027-01-16 05:55:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7c1bc4140aa27c5e0ea50aaa9de89ab911ee9424f26f2d59ff3fd2615be65140
Certificate names · 2 SANs
  • *.dalekane.blog
  • dalekane.blog

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

viewdns.info · 104.21.79.89rapiddns.io
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Kaspersky
SOCRadar
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://dalekane.blog/
Final URL: https://dalekane.blog/
18+ Access
Response
HTTP 200
HTML body
22.5 KB
Compressed
4.7 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4fe56d8fc8adc7d-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 25 Oct 2026 04:04:48 GMT
Last-Modified
Fri, 28 Aug 2026 07:34:06 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=Ux9YDsU%2FzCsg1AP%2F8EO4cpEH%2FLCf42d%2BewvxieyjwZzqYy07Pi2n8IkzuXN3%2Bg%2BdCZ3%2FYPovqppG48JJC96JSTSZbKagP1Ste1WMrlChnhlZJ4yLrq8RbMGAAa4IwWjc"
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived
All retained availability observations1

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    stale_current_evidence
    Monitor confidence
    0
    Original source timestamp
    2026-10-25 05:26:31.922294
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b

Recorded activity

3 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    3/92 engine detections

    View source
  3. Added to PhishDestroy

    dalekane.blog

    View source

Check for cloaking

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

dalekane.blog

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 3 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

Were You Affected by This Site?

4 evidence signal groups linked 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.

Immediate steps Find reporting contacts

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 dalekane.blog)
  • 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

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

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.

Request a correction or appeal How PhishDestroy works
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/dalekane.blog"
  title="PhishDestroy threat report for dalekane.blog"
  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>