Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
ekwa-clientbackup.info favicon

ekwa-clientbackup.info

In short

ekwa-clientbackup.info is a phishing page detected by PhishDestroy on 2026-10-26.

“Ekwa Website Backups”

Registrar
GoDaddy
Resolved IP
72.52.138.42
Registered
Mar 18, 2021
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed Website checks · HTTP 200
VirusTotal detections: 15/92
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Page captures
open gallery
Domain age
Reports sent
No sent record
OTX: 6 refs Oct 26, 2026
X Telegram API

Analysis

Domain summary

ekwa-clientbackup.info is a phishing page detected by PhishDestroy on 2026-10-26. Risk: critical (100/100). Registrar: GoDaddy. Status: Last known active. Hosting: Liquid Web, L.L.C. VirusTotal: 15/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
15 / 92
OTX
6 community refs
Page captures
8

PhishDestroy threat report

Overview

PhishDestroy added ekwa-clientbackup.info to its internal blocklist on 2026-10-26. The recorded page title is “Ekwa Website Backups.” An HTTP 200 response was observed on the same date, indicating the site was reachable at that time.

How the scam works

The domain is flagged by several security vendors as a phishing risk, but no specific malicious behavior was observed on the captured page. In general, phishing sites may impersonate legitimate services to harvest credentials or personal data, though this particular page did not demonstrate such activity.

Evidence

VirusTotal reported 15 malicious detections out of 92 engines on 2026-10-21 and the same count was retrieved on 2026-10-26, with vendors labeling the domain as phishing or malicious. Google Safe Browsing did not flag the domain on 2026-10-26. URLScan’s engine verdict marked the URL as malicious with a score of 37, while its overall verdict was clean on 2026-10-10. Cloudflare Radar classified the site as phishing on 2026-10-26. OTX listed six pulses mentioning the domain as of 2026-10-26. PhishDestroy’s internal list marks the domain as blocked, and external blocklists returned zero matches on the check date.

Infrastructure

The domain was registered on 2021-03-18 through GoDaddy.com, LLC. The recorded IP was 72.52.138.42 and the hosting provider was identified as Liquid Web, L.L.C, located in the United States. The TLS certificate, issued by Let’s Encrypt / YR2, covered *.ekwa-clientbackup.info and was valid from 2026-09-16 to 2026-12-15; DNSSEC was not enabled and the nameservers were ns1.ekwamail.com and ns2.ekwamail.com.

What to do

Do not enter credentials or personal information on the site; if you have already submitted data, monitor affected accounts for suspicious activity and change passwords where applicable. Defenders should block the exact domain, review DNS query logs for accesses to this address, and apply standard phishing mitigation policies.

Source evidenceVirusTotal 15 / 92 · OTX 6 references 8 sources

VirusTotal

15 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
15
Suspicious
0
Undetected
32

Vendor labels

CRDF
malicious
ESET
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
SafeToOpen
phishing
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Registrar

GoDaddy.com, LLC

Created

Expires

Updated

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.ekwamail.com
  • TTL, seconds
    14400
    Type
    MX
    Value
    ekwa-clientbackup.info
    Priority
    0
  • TTL, seconds
    14400
    Type
    A
    Value
    72.52.138.42
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.ekwamail.com
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    support.ekwa.com
    Value
    ns1.ekwamail.com
  • TTL, seconds
    14400
    Type
    TXT
    Value
    v=spf1 +a +mx +ip4:72.52.138.42 ~all

DNS records observed

JARM fingerprint

07d14d16d21d21d07c42d43d000000eeb722fe81b496ebfcfe812e4a988637

Certificate

Subject alternative names
  • *.ekwa-clientbackup.info
  • ekwa-clientbackup.info
Issuer
Let's Encrypt / YR2
Serial
56a9829943b3b58f99f7426cd9ef763261e
SHA-256
a2a63c29ec465d8f0ac1c28664f2693d9a6d14766074c5dda3dd7749f6962286
Subject
*.ekwa-clientbackup.info
Valid until
Valid from

Registration record

Registrar
GoDaddy.com, LLC
Registrar IANA ID
146
Registrar URL
http://www.godaddy.com/domains/search.aspx
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientRenewProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.ekwamail.com
  • ns2.ekwamail.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client delete prohibited
  • client renew prohibited
  • client transfer prohibited
  • client update prohibited
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 15,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "SafeToOpen": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
GoDaddy.com, LLC
Created
2021-03-18T06:13:44Z
Expires
2026-03-18T06:13:44Z
Updated
2025-05-02T06:14:01Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.ekwamail.com"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "ekwa-clientbackup.info",
        "priority": 0
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "72.52.138.42"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.ekwamail.com"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "support.ekwa.com",
        "value": "ns1.ekwamail.com"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:72.52.138.42 ~all"
    }
]
Dns at
2026-10-20T22:21:46Z
Jarm
07d14d16d21d21d07c42d43d000000eeb722fe81b496ebfcfe812e4a988637
Certificate
{
    "san": [
        "*.ekwa-clientbackup.info",
        "ekwa-clientbackup.info"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "56a9829943b3b58f99f7426cd9ef763261e",
    "sha256": "a2a63c29ec465d8f0ac1c28664f2693d9a6d14766074c5dda3dd7749f6962286",
    "subject": "*.ekwa-clientbackup.info",
    "valid_to": "2026-12-15T20:17:49Z",
    "valid_from": "2026-09-16T20:17:50Z"
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146",
    "registrar_url": "http://www.godaddy.com/domains/search.aspx",
    "created": "2021-03-18T06:13:44Z",
    "updated": "2025-05-02T06:14:01Z",
    "expires": "2026-03-18T06:13:44Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.ekwamail.com",
        "ns2.ekwamail.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "expiration": "2027-03-18T06:13:44Z",
        "last changed": "2026-08-11T19:23:46Z",
        "registration": "2021-03-18T06:13:44Z",
        "last update of RDAP database": "2026-10-19T23:39:25Z"
    }
}
Separate source record · 15 malicious + 0 suspicious / 92 · 2026-10-20 22:15:51 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-20T22:15:51Z
fetched_at
2026-10-26T08:31:38Z
stats
{"timeout":0,"harmless":45,"malicious":15,"suspicious":0,"undetected":32}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

27bb6c4a-94f4-42c2-b83b-3c0096c67fd2

Final URL

https://ekwa-clientbackup.info/

HTTP response

200

Navigation history

  • URL
    https://ekwa-clientbackup.info/
    Status
    200

DOM structure hash

d3b0c18fe3cb93650a6b55841b27f9b650d6678c40d65ec8784e8b2525172331

Document hash

6524f50c6cb0202666a518b9c7753ab8d2c802fcff64b31afe02c7a237855927

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    ekwa-clientbackup.info
    Type
    A
    Value
    72.52.138.42

DNSSEC valid

No

IP address

72.52.138.42

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Nameservers
  • ns1.ekwamail.com
  • ns2.ekwamail.com
Original source fields · JSON
Uuid
27bb6c4a-94f4-42c2-b83b-3c0096c67fd2
Final url
https://ekwa-clientbackup.info/
Status
200
History
[
    {
        "url": "https://ekwa-clientbackup.info/",
        "status": 200
    }
]
DOM structure hash
d3b0c18fe3cb93650a6b55841b27f9b650d6678c40d65ec8784e8b2525172331
Document hash
6524f50c6cb0202666a518b9c7753ab8d2c802fcff64b31afe02c7a237855927
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "ekwa-clientbackup.info",
        "type": "A",
        "value": "72.52.138.42"
    }
]
Dnssec valid
false
Ip
72.52.138.42
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2021-03-18T06:13:44Z",
    "updated": "2026-08-11T19:23:46Z",
    "expires": "2027-03-18T06:13:44Z",
    "nameservers": [
        "ns1.ekwamail.com",
        "ns2.ekwamail.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious · engine verdict · score 37

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a17739-89af-700a-9c28-e190dbca2685

Final URL

https://ekwa-clientbackup.info/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://ekwa-clientbackup.info/
    From
    http://ekwa-clientbackup.info/
    Status
    307

IP address

72.52.138.42

Reverse DNS (PTR)

mail.ekwa.com

Contacted IP addresses

  • 72.52.138.42

Autonomous systems (ASN)

  • 32244

Server countries

  • US

Document hash

6cc617be64f449ead43f482b5d1a45f7ebc87d4519ab027906b3e23631f9f620

TLS session and certificate

Subject alternative names
  • *.ekwa-clientbackup.info
  • ekwa-clientbackup.info
Cipher
AES_128_GCM
Issuer
YR2
Subject
*.ekwa-clientbackup.info
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2030

Registered domain age, days

2030

Certificate age, days

39

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
37
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Apache
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a17739-89af-700a-9c28-e190dbca2685
Final url
https://ekwa-clientbackup.info/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://ekwa-clientbackup.info/",
        "from": "http://ekwa-clientbackup.info/",
        "status": 307
    }
]
Ip
72.52.138.42
Ptr
mail.ekwa.com
Contacted IP addresses
[
    "72.52.138.42"
]
Asns
[
    "32244"
]
Countries
[
    "US"
]
Document hash
6cc617be64f449ead43f482b5d1a45f7ebc87d4519ab027906b3e23631f9f620
Tls
{
    "san": [
        "*.ekwa-clientbackup.info",
        "ekwa-clientbackup.info"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "*.ekwa-clientbackup.info",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-15T20:17:49Z",
    "valid_from": "2026-09-16T20:17:50Z"
}
Domain age days
2030
Apex age days
2030
Tls age days
39
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 37,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Apache",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a17739-89af-700a-9c28-e190dbca2685
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

6 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-26T08:37:53Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-26T08:37:53Z
source_timestamp
2026-10-26 09:37:53
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
ekwa-clientbackup.info — Suspicious Domain
ai_description
PhishDestroy flags ekwa-clientbackup.info as a suspicious domain after multiple security vendor detections; the site shows a page titled “Ekwa Website Backups.”.
ai_generated_at
2026-10-26T08:32:47Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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 checksOriginal source recordRetrieved: 22 fields

Mail configuration

MX records
  • ekwa-clientbackup.info
SPF record
v=spf1 +a +mx +ip4:72.52.138.42 ~all
DKIM
  • default
DKIM key size, bits
2048
SPF lookups
2

CAA records

Domain
ekwa-clientbackup.info

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
17
Archived days
28
Snapshots per day
0.02
Average page size, bytes
996

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
Ekwa Website Backups

Trackers

Requests
0

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
222
TLS
122
Waiting
164
Connection
132
Download
0
Response time, ms
640

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 3306

Carbon estimate

Bytes
701
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    72.52.138.42
    Host
    ns1.ekwamail.com
  • IP address
    72.52.138.42
    Host
    ns2.ekwamail.com
DNS zone
ekwa-clientbackup.info

Location

IP address
72.52.138.42
ASN
32244
Organization
Liquid Web, L.L.C
City
Lansing
Country
US

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
*.ekwa-clientbackup.info

DNS records

A
  • 72.52.138.42
MX
  • Mail server
    ekwa-clientbackup.info
    Priority
    0
NS
  • ns2.ekwamail.com
  • ns1.ekwamail.com
SOA
Primary nameserver
ns1.ekwamail.com
Hostmaster
support.ekwa.com
Serial
2026091601
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 +a +mx +ip4:72.52.138.42 ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
72.52.138.42
IP version
4

Redirects

Redirect chain
  • https://ekwa-clientbackup.info

HTTP headers

Response headers
Server
Apache
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "mx": [
        "ekwa-clientbackup.info"
    ],
    "spf": "v=spf1 +a +mx +ip4:72.52.138.42 ~all",
    "dkim": [
        "default"
    ],
    "dkim_bits": 2048,
    "spf_lookups": 2
}
Caa records
{
    "domain": "ekwa-clientbackup.info"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-26T08:00:17Z",
    "first": "2021-12-02T19:22:58Z",
    "changes": 17,
    "days_archived": 28,
    "scans_per_day": 0.02,
    "avg_page_bytes": 996
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Ekwa Website Backups"
}
Trackers
{
    "requests": 0
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 222,
        "tls": 122,
        "wait": 164,
        "connect": 132,
        "download": 0
    },
    "response_ms": 640
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Carbon
{
    "bytes": 701,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "72.52.138.42",
            "host": "ns1.ekwamail.com"
        },
        {
            "ip": "72.52.138.42",
            "host": "ns2.ekwamail.com"
        }
    ],
    "zone": "ekwa-clientbackup.info"
}
Location
{
    "ip": "72.52.138.42",
    "asn": "32244",
    "org": "Liquid Web, L.L.C",
    "city": "Lansing",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "*.ekwa-clientbackup.info"
}
DNS records
{
    "A": [
        "72.52.138.42"
    ],
    "MX": [
        "{\"exchange\": \"ekwa-clientbackup.info\", \"priority\": 0}"
    ],
    "NS": [
        "ns2.ekwamail.com",
        "ns1.ekwamail.com"
    ],
    "SOA": "{\"nsname\": \"ns1.ekwamail.com\", \"hostmaster\": \"support.ekwa.com\", \"serial\": 2026091601, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 +a +mx +ip4:72.52.138.42 ~all"
    ]
}
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
}
Get ip
{
    "ip": "72.52.138.42",
    "family": 4
}
Redirects
{
    "chain": [
        "https://ekwa-clientbackup.info"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Apache",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about ekwa-clientbackup.info

Is ekwa-clientbackup.info legit?

No. PhishDestroy classifies ekwa-clientbackup.info as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-26. VirusTotal: 15/92 engines flag it. Treat the site as unsafe.

Is ekwa-clientbackup.info safe to connect a wallet?

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

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 · 8 captures

All capture links and hashes (8)

Domain details

Domain
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar GoDaddy US(US)
Hosting abuse contact abuse@liquidweb.com Liquid Web, L.L.C · AS32244
RegistrationCreated Mar 18, 2021 — Expires Mar 18, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 0/100
Submitted URLhttp://ekwa-clientbackup.info/
Case ID
Observed page title
Ekwa Website Backups
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 50 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
72.52.138.42
Network ASN
AS32244
Organization
Liquid Web, L.L.C
Observed location
Lansing, US
Server header
Apache

Nameservers 2

  • ns1.ekwamail.com
  • ns2.ekwamail.com

Mail routing 1 MX record

  • ekwa-clientbackup.infopriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-16 20:17:50
Valid until
2026-12-15 20:17:49
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-26 08:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta2a63c29ec465d8f0ac1c28664f2693d9a6d14766074c5dda3dd7749f6962286
Certificate names · 2 SANs
  • *.ekwa-clientbackup.info
  • ekwa-clientbackup.info

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
SafeToOpen
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ekwa-clientbackup.info · checked Oct 26, 2026

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.63 s
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://ekwa-clientbackup.info/
Ekwa Website Backups
Response
HTTP 200
HTML body
701 B
Compressed
442 B
Links
0 internal · 0 external
Detected technologies
apache
Selected response headers
Server: Apache
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 6cc617be64f449ead43f482b5d1a45f7ebc87d4519ab027906b3e23631f9f620
Saved response-header values · 8
Connection
Keep-Alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Mon, 26 Oct 2026 08:00:06 GMT
Keep-Alive
timeout=2, max=500
Server
Apache
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:01:14.000000
    Evidence SHA-256
    ba3dc5a2024183100ebbc18266e99304d9d6e026ed3381179a1535417cc3019b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 09:01:14
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:01:14.000000
    Evidence SHA-256
    ba3dc5a2024183100ebbc18266e99304d9d6e026ed3381179a1535417cc3019b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 09:01:14
    Evidence reason

Recorded activity

6 entries
  1. AlienVault OTX

    6 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. VirusTotal

    15/92 engine detections

    View source
  4. Added to PhishDestroy

    ekwa-clientbackup.info

    View source
  5. URLScan

    Page captured

    View source
  6. Wayback Machine

    Page archived

    View source
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.

Check for cloaking

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

ekwa-clientbackup.info

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
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

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

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 ekwa-clientbackup.info)
  • 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

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.

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/ekwa-clientbackup.info"
  title="PhishDestroy threat report for ekwa-clientbackup.info"
  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>