Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
clientesseguros.blog favicon

clientesseguros.blog

In short

clientesseguros.blog is a credential phishing page detected by PhishDestroy on 2026-10-24.

“Your domain is suspended”

Review the evidence
Registrar
Hostinger
Resolved IP
2.57.91.93
Registered
Apr 20, 2026
PhishDestroy assessment Critical
First observed Oct 24, 2026 14:31 UTC · PhishDestroy
Risk signals
VirusTotal detections: 13/92 Scam type: Credential Phishing
VirusTotal
13 / 92
engine detections ·
OTX
5
community references
Cloudflare Radar
clean
source verdict
Page captures
5
open gallery
Domain age
188 days
Reports sent
1
view timeline
OTX: 5 refs Oct 24, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 24H+ 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@hostinger.com. The latest stored availability evidence still shows the domain reachable; 43 hours 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
43 hours
Reports sent
1
Latest case ID
PD-20261024-44E0DD
Current status
Observed active at latest stored check

Analysis

Domain summary

clientesseguros.blog is a credential phishing page detected by PhishDestroy on 2026-10-24. Risk: critical (89/100). Registrar: Hostinger. Hosting: Hostinger International Limited. PhishDestroy sent 1 abuse report. VirusTotal: 13/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
13 / 92
OTX
5 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed clientesseguros.blog as a suspicious domain based on multiple malicious detections. The recorded page title is “Your domain is suspended”. The domain was first observed by PhishDestroy on 2026-10-24 and returned an HTTP 200 response on that date.

How the scam works

The detections indicate the site could be used for phishing or malware distribution, which are common tactics for suspicious domains. No specific credential‑stealing form or malicious payload was observed; the page only displays a generic suspension notice.

Evidence

VirusTotal scans on 2026-10-18 and 2026-10-24 each reported 13 malicious detections out of 92 engines, with vendors labeling the domain as phishing or malware. Google Safe Browsing checked on 2026-10-24 did not flag the site. urlscan captured the site on 2026-10-24 and gave an overall clean verdict, though its engine score was 97 and it tagged the URL as malicious. OTX listed five pulses referencing the domain as of 2026-10-24. PhishDestroy’s internal blocklist includes the domain, while external blocklists returned no matches.

Infrastructure

The domain was registered on 2026-04-20 through HOSTINGER operations, UAB, using verification‑hold nameservers ns1.verification-hold.dns-suspended.com and ns2.verification-hold.dns-suspended.com. The recorded A record points to 2.57.91.93, owned by Hostinger International Limited in the United States, and the site presented a Let’s Encrypt certificate valid until 2027-01-01. DNSSEC is not enabled for the zone.

What to do

Visitors should not enter credentials or download files from the site; if any information was submitted, change associated passwords and monitor accounts for unusual activity. Defenders can add clientesseguros.blog to perimeter blocklists and monitor server logs for connections to 2.57.91.93. Ensure that internal credentials have not been reused on this domain and apply standard phishing‑awareness controls.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-24T14:36:55Z)VirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 13 / 92 · OTX 5 references 9 sources

VirusTotal

13 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
13
Suspicious
0
Undetected
33

Vendor labels

DNS8
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
LevelBlue
phishing
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

-7

Community votes

Malicious
1

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

HOSTINGER operations, UAB

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    2.57.91.93
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    hostmaster.hostinger.com
    Value
    ns1.verification-hold.dns-suspended.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.verification-hold.dns-suspended.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.verification-hold.dns-suspended.com
  • TTL, seconds
    3600
    Type
    TXT
    Value
    This domain is under verification hold by Hostinger!

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d

Certificate

Subject alternative names
  • clientesseguros.blog
  • www.clientesseguros.blog
Issuer
Let's Encrypt / YE2
Serial
5e78e0c92519882cff4547586b7cff17371
SHA-256
9bd6e9f46e91b3e7849a7cb4744dac1596d570414b7dd44d8695a26595a78e03
Subject
clientesseguros.blog
Valid until
Valid from

Registration record

Registrar
HOSTINGER operations, UAB
Registrar IANA ID
1636
Registrar URL
https://www.hostinger.com/
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1.verification-hold.dns-suspended.com
  • ns2.verification-hold.dns-suspended.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
  • server transfer prohibited
Registry events
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 13,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "DNS8": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
-7
Votes
{
    "malicious": 1
}
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
HOSTINGER operations, UAB
Created
2026-04-20T15:26:56Z
Expires
2027-04-20T15:26:56Z
Updated
2026-06-19T15:30:41Z
First seen
2026-04-20T15:49:29Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "2.57.91.93"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "hostmaster.hostinger.com",
        "value": "ns1.verification-hold.dns-suspended.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.verification-hold.dns-suspended.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.verification-hold.dns-suspended.com"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "This domain is under verification hold by Hostinger!"
    }
]
Dns at
2026-10-17T23:48:39Z
Jarm
27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "clientesseguros.blog",
        "www.clientesseguros.blog"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5e78e0c92519882cff4547586b7cff17371",
    "sha256": "9bd6e9f46e91b3e7849a7cb4744dac1596d570414b7dd44d8695a26595a78e03",
    "subject": "clientesseguros.blog",
    "valid_to": "2027-01-01T12:10:37Z",
    "valid_from": "2026-10-03T12:10:38Z"
}
Registration record
{
    "registrar": "HOSTINGER operations, UAB",
    "registrar_iana_id": "1636",
    "registrar_url": "https://www.hostinger.com/",
    "created": "2026-04-20T15:26:56Z",
    "updated": "2026-06-19T15:30:41Z",
    "expires": "2027-04-20T15:26:56Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.verification-hold.dns-suspended.com",
        "ns2.verification-hold.dns-suspended.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "server transfer prohibited"
    ],
    "events": {
        "registration": "2026-04-20T15:26:56Z",
        "registrar expiration": "2027-04-20T15:26:56Z",
        "last update of RDAP database": "2026-05-06T08:40:31Z"
    }
}
Separate source record · 13 malicious + 0 suspicious / 92 · 2026-10-17 23:48:25 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-17T23:48:25Z
fetched_at
2026-10-24T15:37:13Z
stats
{"timeout":0,"harmless":46,"malicious":13,"suspicious":0,"undetected":33}

URLScan

Malicious · engine verdict · score 97

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

01a16e5d-98d5-7486-8721-24c44f2b7026

Final URL

http://clientesseguros.blog/

HTTP response

200

Redirects

  • To
    https://clientesseguros.blog/
    From
    http://clientesseguros.blog/
    Status
    307
  • To
    http://clientesseguros.blog/
    From
    https://clientesseguros.blog/
    Status
    307

IP address

2.57.91.93

Contacted domains

  • maxcdn.bootstrapcdn.com
  • fonts.googleapis.com
  • fonts.gstatic.com
  • www.googletagmanager.com
  • ajax.googleapis.com

Contacted IP addresses

  • 142.251.14.94
  • 142.251.13.97
  • 142.251.127.95
  • 142.251.20.95
  • 104.18.11.207
  • 2.57.91.93

Autonomous systems (ASN)

  • 15169
  • 13335
  • 47583

Server countries

  • US
  • CY

Linked domains

  • www.hostinger.com
  • hpanel.hostinger.com
  • support.hostinger.com

Document hash

04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

JavaScript globals

  • $
  • jQuery
  • gtag
  • dataLayer
  • punycode
  • pathName
  • account
  • google_tag_data
  • google_tag_manager

Domain age, days

186

Registered domain age, days

186

Page requests

15

Provider verdicts

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

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a16e5d-98d5-7486-8721-24c44f2b7026
Final url
http://clientesseguros.blog/
Status
200
Redirects
[
    {
        "to": "https://clientesseguros.blog/",
        "from": "http://clientesseguros.blog/",
        "status": 307
    },
    {
        "to": "http://clientesseguros.blog/",
        "from": "https://clientesseguros.blog/",
        "status": 307
    }
]
Ip
2.57.91.93
Contacted domains
[
    "maxcdn.bootstrapcdn.com",
    "fonts.googleapis.com",
    "fonts.gstatic.com",
    "www.googletagmanager.com",
    "ajax.googleapis.com"
]
Contacted IP addresses
[
    "142.251.14.94",
    "142.251.13.97",
    "142.251.127.95",
    "142.251.20.95",
    "104.18.11.207",
    "2.57.91.93"
]
Asns
[
    "15169",
    "13335",
    "47583"
]
Countries
[
    "US",
    "CY"
]
Linked domains
[
    "www.hostinger.com",
    "hpanel.hostinger.com",
    "support.hostinger.com"
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Globals
[
    "$",
    "jQuery",
    "gtag",
    "dataLayer",
    "punycode",
    "pathName",
    "account",
    "google_tag_data",
    "google_tag_manager"
]
Domain age days
186
Apex age days
186
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
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
01a101e3-25a6-7614-bdab-b542ec716ba7
score
null
malicious
null
result_at
null
enriched_at
2026-10-25T09:14:59Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-25 10:14:59"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

5 community references

Open report

Cloudflare Radar

provider verdict: clean

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

8af02fd2-4a71-409d-a087-ad2390831c55

Final URL

https://clientesseguros.blog/

HTTP response

200

Navigation history

  • URL
    https://clientesseguros.blog/
    Status
    200

DOM structure hash

9ff7b3096ce9f087cbac82412f8eb8e8ff898089cc44f84903ee59988d2197ad

Document hash

3011048bc7d90c1a242cf19af7b4cfd62141ecfd8510e638f4789f3286cc6f2b

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    clientesseguros.blog
    Type
    A
    Value
    2.57.91.93

DNSSEC valid

No

IP address

2.57.91.93

Registration record

Registrar
HOSTINGER operations, UAB
Registered
Updated
Expires
Nameservers
  • ns1.verification-hold.dns-suspended.com
  • ns2.verification-hold.dns-suspended.com
Original source fields · JSON
Uuid
8af02fd2-4a71-409d-a087-ad2390831c55
Final url
https://clientesseguros.blog/
Status
200
History
[
    {
        "url": "https://clientesseguros.blog/",
        "status": 200
    }
]
DOM structure hash
9ff7b3096ce9f087cbac82412f8eb8e8ff898089cc44f84903ee59988d2197ad
Document hash
3011048bc7d90c1a242cf19af7b4cfd62141ecfd8510e638f4789f3286cc6f2b
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "clientesseguros.blog",
        "type": "A",
        "value": "2.57.91.93"
    }
]
Dnssec valid
false
Ip
2.57.91.93
Registration record
{
    "registrar": "HOSTINGER operations, UAB",
    "created": "2026-04-20T15:26:56Z",
    "updated": "2026-06-19T15:30:41Z",
    "expires": "2027-04-20T15:26:56Z",
    "nameservers": [
        "ns1.verification-hold.dns-suspended.com",
        "ns2.verification-hold.dns-suspended.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

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
clientesseguros.blog — Suspicious Domain
ai_description
PhishDestroy flagged clientesseguros.blog as suspicious after VirusTotal reported 13 malicious detections, the site displays a “Your domain is suspended” page.
ai_generated_at
2026-10-24T15:39:56Z
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: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
clientesseguros.blog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
4637

Crawler rules

User agents
  • *
Present
Yes

Security contact file (security.txt)

Present
Yes
Found at
/.well-known/security.txt

Page title and metadata

Page title
Your domain is suspended
Description
Domain is suspended

Forms and mixed content

Scripts without SRI
  • https://www.googletagmanager.com/gtag/js
  • https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
  • https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js
Third-party scripts
3

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
270
TLS
40
Waiting
13
Connection
5
Download
0
Response time, ms
328

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
10390
CO₂, grams
0.0004
Cleaner than, %
71

DNS servers

Nameservers
  • IP address
    217.21.79.23
    Host
    ns2.verification-hold.dns-suspended.com
  • IP address
    217.65.148.101
    Host
    ns1.verification-hold.dns-suspended.com
DNS zone
clientesseguros.blog

Location

IP address
2.57.91.93
ASN
47583
Organization
Hostinger International Limited
City
Washington
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
clientesseguros.blog

DNS records

A
  • 2.57.91.93
NS
  • ns2.verification-hold.dns-suspended.com
  • ns1.verification-hold.dns-suspended.com
SOA
Primary nameserver
ns1.verification-hold.dns-suspended.com
Hostmaster
hostmaster.hostinger.com
Serial
2023081800
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
3600
TXT
  • This domain is under verification hold by Hostinger!

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
2.57.91.93
IP version
4

Redirects

Redirect chain
  • https://clientesseguros.blog

Page links

External link addresses
  • https://www.hostinger.com/
  • https://www.hostinger.com/web-hosting
  • https://www.hostinger.com/domain-name-search
  • https://www.hostinger.com/business-email
  • https://www.hostinger.com/vps-hosting
  • https://hpanel.hostinger.com/
  • https://support.hostinger.com/en/articles/1583442-how-to-fix-a-domain-suspended-due-to-pending-icann-verification
  • https://support.hostinger.com/en/articles/1583443-how-to-verify-domain-registrant-s-contact-details
External links
8

Registration record

Registrar
HOSTINGER operations, UAB
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.verification-hold.dns-suspended.com
  • ns2.verification-hold.dns-suspended.com

HTTP headers

Response headers
Server
hcdn
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "clientesseguros.blog"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-24T14:33:58Z",
    "first": "2026-10-24T14:33:58Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4637
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Security contact file
{
    "present": true,
    "found_in": "/.well-known/security.txt"
}
Page title and metadata
{
    "title": "Your domain is suspended",
    "description": "Domain is suspended"
}
Forms and mixed content
{
    "no_sri": [
        "https://www.googletagmanager.com/gtag/js",
        "https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js",
        "https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"
    ],
    "third_party_scripts": 3
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 270,
        "tls": 40,
        "wait": 13,
        "connect": 5,
        "download": 0
    },
    "response_ms": 328
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 10390,
    "co2_grams": 0.0004,
    "cleaner_than": 71
}
Dns server
{
    "ns": [
        {
            "ip": "217.21.79.23",
            "host": "ns2.verification-hold.dns-suspended.com"
        },
        {
            "ip": "217.65.148.101",
            "host": "ns1.verification-hold.dns-suspended.com"
        }
    ],
    "zone": "clientesseguros.blog"
}
Location
{
    "ip": "2.57.91.93",
    "asn": "47583",
    "org": "Hostinger International Limited",
    "city": "Washington",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "clientesseguros.blog"
}
DNS records
{
    "A": [
        "2.57.91.93"
    ],
    "NS": [
        "ns2.verification-hold.dns-suspended.com",
        "ns1.verification-hold.dns-suspended.com"
    ],
    "SOA": "{\"nsname\": \"ns1.verification-hold.dns-suspended.com\", \"hostmaster\": \"hostmaster.hostinger.com\", \"serial\": 2023081800, \"refresh\": 10800, \"retry\": 3600, \"expire\": 604800, \"minttl\": 3600}",
    "TXT": [
        "This domain is under verification hold by Hostinger!"
    ]
}
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": "2.57.91.93",
    "family": 4
}
Redirects
{
    "chain": [
        "https://clientesseguros.blog"
    ]
}
Page links
{
    "external": [
        "https://www.hostinger.com/",
        "https://www.hostinger.com/web-hosting",
        "https://www.hostinger.com/domain-name-search",
        "https://www.hostinger.com/business-email",
        "https://www.hostinger.com/vps-hosting",
        "https://hpanel.hostinger.com/",
        "https://support.hostinger.com/en/articles/1583442-how-to-fix-a-domain-suspended-due-to-pending-icann-verification",
        "https://support.hostinger.com/en/articles/1583443-how-to-verify-domain-registrant-s-contact-details"
    ],
    "external_count": 8
}
Registration record
{
    "registrar": "HOSTINGER operations, UAB",
    "created": "2026-04-20T15:26:56Z",
    "updated": "2026-06-19T15:30:41Z",
    "expires": "2027-04-20T15:26:56Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.verification-hold.dns-suspended.com",
        "ns2.verification-hold.dns-suspended.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "hcdn",
        "content-type": "text/html"
    }
}

Questions about clientesseguros.blog

Is clientesseguros.blog legit?

No. PhishDestroy classifies clientesseguros.blog as a credential phishing page (risk: critical, 89/100); it was first detected on 2026-10-24. VirusTotal: 13/92 engines flag it. Treat the site as unsafe.

Is clientesseguros.blog safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on clientesseguros.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 clientesseguros.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 · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)
Observed page title
Your domain is suspended
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 67 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 24, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Hostinger LT(LT)
Abuse contactabuse@hostinger.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for clientesseguros.blog →
Hosting abuse contact abuse@hostinger.com Hostinger International Limited · AS47583
RegistrationCreated Apr 20, 2026 (188d) — Expires Apr 20, 2027
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 20/100
Submitted URLhttp://clientesseguros.blog/
Case ID
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

Resolved IP
2.57.91.93
Network ASN
AS47583
Organization
Hostinger International Limited
Observed location
Washington, US
Server header
hcdn

Nameservers 2

  • ns1.verification-hold.dns-suspended.com
  • ns2.verification-hold.dns-suspended.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-03 12:10:38
Valid until
2027-01-01 12:10:37
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9bd6e9f46e91b3e7849a7cb4744dac1596d570414b7dd44d8695a26595a78e03
Certificate names · 2 SANs
  • clientesseguros.blog
  • www.clientesseguros.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 · 2.57.91.93rapiddns.io

Latest Classified Outcome 2026-10-25 20:55:07 UTC

The domain no longer resolves in DNS.

Technical details
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-25 23:00:40 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-24 14:45:08 UTC current episode first observed: 2026-10-24 20:55:07 UTC observed RIP window: 2026-10-24 14:45:08 UTC → 2026-10-24 20:55:07 UTC · 6.17h midpoint estimate ≈ 2026-10-24 17:50:07 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.clientesseguros.blogDomain record

The original observation time is not recorded for these hostnames.

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CyRadar
DNS8
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of clientesseguros.blog · checked Oct 24, 2026

71
Needs Work
Performance
FCP
2.8 s
First Contentful Paint
LCP
6.42 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
125 ms
Total Blocking Time
SI
2.8 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://clientesseguros.blog/
Your domain is suspended
Domain is suspended
Response
HTTP 200
HTML body
10.1 KB
Compressed
3.8 KB
Links
0 internal · 8 external
Detected technologies
jquerybootstrap
Selected response headers
Content-Type: text/html
Cache-Control: no-store
Content-Encoding: gzip
Server: hcdn
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 3011048bc7d90c1a242cf19af7b4cfd62141ecfd8510e638f4789f3286cc6f2b
Saved response-header values · 10
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store
Connection
close
Content-Encoding
gzip
Content-Type
text/html
Date
Sat, 24 Oct 2026 14:33:37 GMT
Server
hcdn
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-hcdn-request-id
f4cb2807d3247ecffc1dc69b29737667-bnk-edge8

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

Archived
Registration & observation details8

Availability observations

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

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

Stored observation history2

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

All retained availability observations8

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. 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 00:00:40.000000
    Evidence SHA-256
    c5efdd6e2484c4fe5e07dadc0ef356a51d2e88c34955a91e3df500b628eb2fbc
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 00:00:40
    Evidence reason
    unavailable
  2. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 21:55:07.813656
    Evidence SHA-256
    217ad76bc4720c4dba0457a7c668ca3526212919fc22f96152c34b0de91e9080
    Evidence timestamp as recorded
    2026-10-25 21:55:07.813656
  3. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 21:55:07.813656
    Evidence SHA-256
    217ad76bc4720c4dba0457a7c668ca3526212919fc22f96152c34b0de91e9080
    Evidence timestamp as recorded
    2026-10-25 21:55:07.813656
  4. 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-25 12:00:43.000000
    Evidence SHA-256
    ca747efc2186c11cc16c44539348f198998ae7ed91450d1a0705128e4d7357cb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 12:00:43
    Evidence reason
    unavailable
  5. 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-25 01:07:06.000000
    Evidence SHA-256
    249d97dd7d86f993bcaa0184245e8a7d435349d1b6d44de0bc516288548d3188
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 01:07:06
    Evidence reason
    unavailable
  6. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 22:55:07.425478
    Evidence SHA-256
    8185bc2cd7a3c765180d1729f338df90ac7b020fbf87517599d31d90ea0d7abf
    Evidence timestamp as recorded
    2026-10-24 22:55:07.425478
  7. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 22:55:07.425478
    Evidence SHA-256
    8185bc2cd7a3c765180d1729f338df90ac7b020fbf87517599d31d90ea0d7abf
    Evidence timestamp as recorded
    2026-10-24 22:55:07.425478
  8. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 16:36:36.130568
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Recorded activity

6 entries
  1. AlienVault OTX

    5 community references

    View source
  2. VirusTotal

    13/92 engine detections

    View source
  3. Abuse report sent

    PD-20261024-44E0DD

    abuse@hostinger.com
  4. URLScan

    Page captured

    View source
  5. Wayback Machine

    Page archived

    View source
  6. Added to PhishDestroy

    clientesseguros.blog

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

clientesseguros.blog

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 13 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 5 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261024-44E0DD Recipient: abuse@hostinger.com
PDF notice generated
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?

6 evidence signal groups linked 1 stored notification records Unverified
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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

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.

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