Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
es-seguridad.webflow.io favicon

es-seguridad.webflow.io

In short

es-seguridad.webflow.io is a phishing page detected by PhishDestroy on 2026-10-25.

“es-seguridad”

Review the evidence
Registrar
MalaysiaWebflow
Resolved IP
United Kingdom104.18.36.248Cloudflare, Inc. · CDN
Registered
May 8, 2013
First observed
Oct 25, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 16/92
VirusTotal
16 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 94
Page captures
4
open gallery
Domain age
4,920 days
Oct 25, 2026 CDN
X Telegram API

Analysis

Domain summary

es-seguridad.webflow.io is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Webflow. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
16 / 92
Hosting
United Kingdom104.18.36.248Cloudflare, Inc. · CDN
Registrar
MalaysiaWebflow
Registered
May 8, 2013
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated intake flagged the site as malicious because it presented a “PORTAL DE VALIDACIÓN DE CORREO ELECTRÓNICO” that asks for an email address and password, a common credential‑theft lure. The prior assessment recorded this reasoning on 2026-10-25. The page was first seen by PhishDestroy on 2026-10-25, returned HTTP 200 and had the title “es-seguridad”.

How the scam works

Credential‑phishing attacks host a fake login portal that mimics a legitimate service and prompt victims to enter their credentials. Harvested email addresses and passwords can be used to hijack accounts, bypass two‑factor authentication, or be sold on underground markets.

Evidence

VirusTotal scanned the domain on 2026-10-13 and reported 16 malicious detections out of 92 engines, with no suspicious results. Google Safe Browsing checked the URL on 2026-10-26 and did not flag it. urlscan.io captured the page twice: the 2026-10-23 capture received a clean verdict, while the 2026-10-25 capture triggered a machine‑learning engine score of 94 and a malicious tag, though the overall verdict remained non‑malicious. PhishDestroy’s internal blocklist listed the domain, while external blocklists returned zero hits on the dates checked. OTX recorded zero pulses for the domain.

Infrastructure

The recorded IP was 172.64.151.8 and the network was identified as Cloudflare (CLOUDFLARENET, US). TLS was provided by Google Trust Services with a certificate valid until 2026-12-21. The domain had been registered for 368 days and the apex domain for 4,207 days; the TLS certificate was 33 days old at the time of observation.

What to do

Anyone who may have entered credentials on this page should change the associated password immediately, enable multi‑factor authentication, and monitor the account for unauthorized activity. Organizations should block the domain at the network perimeter, add it to threat‑intel feeds, and review logs for outbound requests to the recorded IP or host. Continue to monitor the domain for changes, as the current evidence reflects a snapshot in time.

Useful links

urlscan.io scan and screenshotStored capture screenshotURLScan screenshot (2026-10-23T05:18:27Z)URLScan capture reportURLScan screenshot (2026-10-25T19:24:39Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 16 / 92 7 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
16
Suspicious
0
Undetected
30

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a06:98c1:3102::ac40:9708
  • TTL, seconds
    300
    Type
    A
    Value
    172.64.151.8
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a06:98c1:3105::6812:24f8
  • TTL, seconds
    300
    Type
    A
    Value
    104.18.36.248

DNS records observed

JARM fingerprint

27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • webflow.io
  • *.webflow.io
Issuer
Google Trust Services / WE1
Serial
ac972ef95a18ab8f0e5a2917e958d6da
SHA-256
5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7
Subject
webflow.io
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • journey.ns.cloudflare.com
  • lamar.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 16,
    "suspicious": 0,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2013-05-08T02:20:57Z
Expires
2028-05-08T02:20:57Z
Updated
2026-08-12T04:04:30Z
First seen
2025-10-14T11:49:29Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3102::ac40:9708"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.64.151.8"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3105::6812:24f8"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.18.36.248"
    }
]
Dns at
2026-10-13T09:44:47Z
Jarm
27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "webflow.io",
        "*.webflow.io"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "ac972ef95a18ab8f0e5a2917e958d6da",
    "sha256": "5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7",
    "subject": "webflow.io",
    "valid_to": "2026-12-21T03:46:57Z",
    "valid_from": "2026-09-22T02:47:08Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-05-08T02:20:57Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2028-05-08T02:20:57Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "journey.ns.cloudflare.com",
        "lamar.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 16 malicious + 0 suspicious / 92 · 2026-10-13 09:38: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-13T09:38:25Z
fetched_at
2026-10-25T19:39:27Z
stats
{"timeout":0,"harmless":46,"malicious":16,"suspicious":0,"undetected":30}

URLScan

Malicious · engine verdict · score 94

SHA-256 e97c1566a6f741d9c8767d64a5f7f59d56996311c616d280acf8e894b653f98f

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a17484-2ab0-7003-a41a-06ff2d2b06b7

Final URL

https://es-seguridad.webflow.io/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://es-seguridad.webflow.io/
    From
    http://es-seguridad.webflow.io/
    Status
    307

IP address

172.64.151.8

Contacted domains

  • challenges.cloudflare.com
  • d3e54v103j8qbb.cloudfront.net
  • cdn.prod.website-files.com

Contacted IP addresses

  • 104.18.95.41
  • 13.33.25.120
  • 104.18.94.41
  • 13.33.25.64
  • 104.18.161.117
  • 172.64.151.8

Autonomous systems (ASN)

  • 13335
  • 16509

Server countries

  • US

Linked domains

  • webflow.com

Document hash

cede1f6867d7422cd512e6479aab328b83f990811c08a54f4ddcbc35dafb4450

JavaScript globals

  • $
  • jQuery
  • tram
  • Webflow
  • turnstile

TLS session and certificate

Subject alternative names
  • webflow.io
  • *.webflow.io
Cipher
AES_128_GCM
Issuer
WE1
Subject
webflow.io
Protocol
QUIC
Valid until
Valid from

Domain age, days

368

Registered domain age, days

4207

Certificate age, days

33

Certificate validity, days

90

Page requests

9

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Content-security-policy
frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com
Original source fields · JSON
Uuid
01a17484-2ab0-7003-a41a-06ff2d2b06b7
Final url
https://es-seguridad.webflow.io/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://es-seguridad.webflow.io/",
        "from": "http://es-seguridad.webflow.io/",
        "status": 307
    }
]
Ip
172.64.151.8
Contacted domains
[
    "challenges.cloudflare.com",
    "d3e54v103j8qbb.cloudfront.net",
    "cdn.prod.website-files.com"
]
Contacted IP addresses
[
    "104.18.95.41",
    "13.33.25.120",
    "104.18.94.41",
    "13.33.25.64",
    "104.18.161.117",
    "172.64.151.8"
]
Asns
[
    "13335",
    "16509"
]
Countries
[
    "US"
]
Linked domains
[
    "webflow.com"
]
Document hash
cede1f6867d7422cd512e6479aab328b83f990811c08a54f4ddcbc35dafb4450
Globals
[
    "$",
    "jQuery",
    "tram",
    "Webflow",
    "turnstile"
]
Tls
{
    "san": [
        "webflow.io",
        "*.webflow.io"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "webflow.io",
    "protocol": "QUIC",
    "valid_to": "2026-12-21T03:46:57Z",
    "valid_from": "2026-09-22T02:47:08Z"
}
Domain age days
368
Apex age days
4207
Tls age days
33
Tls valid days
90
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "content-security-policy": "frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com"
}
Separate monitor record · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17484-2ab0-7003-a41a-06ff2d2b06b7
score
0
malicious
false
result_at
2026-10-26T04:30:20Z
enriched_at
2026-10-26T09:13:34Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:20","urlscan_enriched_at":"2026-10-26 10:13:34"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T23:20:12Z

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-25T23:20:12Z
source_timestamp
2026-10-26 00:20:12
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
es-seguridad.webflow.io — Credential Phishing Page
ai_description
PhishDestroy flagged es-seguridad.webflow.io for presenting an email validation portal that asks for email and password, indicating credential‑phishing risk.
ai_generated_at
2026-10-27T02:42:52Z
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

SPF lookups
0

CAA records

Domain
es-seguridad.webflow.io

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Page title and metadata

Page title
es-seguridad
Generator
Webflow

Trackers

Requests
10
Observed services
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    3
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    4
  • Name
    Webflow
    Company
    Webflow
    Country
    US
    Category
    Hosting
    Requests
    3

Forms and mixed content

Scripts without SRI
  • https://cdn.prod.website-files.com/68ee15040c7856c805cd817a/js/webflow.a0aa6ca1.4aaf0738f166d3e2.js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
23
Waiting
60
Connection
16
Download
0
Response time, ms
101

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
  • 8080

Carbon estimate

Bytes
2648
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    172.64.35.142
    Host
    lamar.ns.cloudflare.com
  • IP address
    172.64.34.3
    Host
    journey.ns.cloudflare.com
DNS zone
webflow.io

Location

IP address
2a06:98c1:3105::6812:24f8
ASN
13335
Organization
Cloudflare, Inc.
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
webflow.io

DNS records

A
  • 104.18.36.248
  • 172.64.151.8
AAAA
  • 2a06:98c1:3102::ac40:9708
  • 2a06:98c1:3105::6812:24f8

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
frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3105::6812:24f8
IP version
6

Redirects

Redirect chain
  • https://es-seguridad.webflow.io

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
Content-security-policy
frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "es-seguridad.webflow.io"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T19:08:41Z",
    "first": "2026-10-25T19:08:41Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2433
}
Page title and metadata
{
    "title": "es-seguridad",
    "generator": "Webflow"
}
Trackers
{
    "requests": 10,
    "trackers": [
        {
            "name": "Amazon CloudFront",
            "company": "Amazon",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        },
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        },
        {
            "name": "Webflow",
            "company": "Webflow",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.prod.website-files.com/68ee15040c7856c805cd817a/js/webflow.a0aa6ca1.4aaf0738f166d3e2.js"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 23,
        "wait": 60,
        "connect": 16,
        "download": 0
    },
    "response_ms": 101
}
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,
        8080
    ]
}
Carbon
{
    "bytes": 2648,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.35.142",
            "host": "lamar.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.3",
            "host": "journey.ns.cloudflare.com"
        }
    ],
    "zone": "webflow.io"
}
Location
{
    "ip": "2a06:98c1:3105::6812:24f8",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "webflow.io"
}
DNS records
{
    "A": [
        "104.18.36.248",
        "172.64.151.8"
    ],
    "AAAA": [
        "2a06:98c1:3102::ac40:9708",
        "2a06:98c1:3105::6812:24f8"
    ]
}
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": "frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow",
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3105::6812:24f8",
    "family": 6
}
Redirects
{
    "chain": [
        "https://es-seguridad.webflow.io"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "content-security-policy": "frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com"
    }
}

Questions about es-seguridad.webflow.io

Is es-seguridad.webflow.io legit?

No. PhishDestroy classifies es-seguridad.webflow.io as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 16/92 engines flag it. Treat the site as unsafe.

Is es-seguridad.webflow.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on es-seguridad.webflow.io. 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 es-seguridad.webflow.io?

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 · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
es-seguridad.webflow.io: caution — 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card es-seguridad.webflow.io: caution — 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 28b94f42ddf7

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 94 report ↗
IP Context United Kingdom104.18.36.248 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Webflow MY(MY)
Abuse contactabuse@webflow.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for webflow.io →
Registration (base domain)webflow.io · Created May 8, 2013 — Expires May 8, 2028
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 26, 2026score 93/100
Submitted URLhttp://es-seguridad.webflow.io/
Observed page title
es-seguridad
TLS Certificate
Issued by WE1 · stored validity ends in 54 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom104.18.36.248
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-09-22 02:47:08
Valid until
2026-12-21 03:46:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7
Certificate names · 2 SANs
  • webflow.io
  • *.webflow.io

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.18.36.248rapiddns.io

Latest Classified Outcome 2026-10-27 11:03:27 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-27 11:03:27 UTC
RDAP registration
Observed timeline last reachable: 2026-10-26 00:19:49 UTC last content: 2026-10-26 00:19:49 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
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://es-seguridad.webflow.io/
Final URL: https://es-seguridad.webflow.io/
es-seguridad
Response
HTTP 200
HTML body
2.6 KB
Compressed
1.3 KB
Links
0 internal · 0 external
Detected technologies
jquerycloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
CF-Cache-Status: HIT
Content-Encoding: gzip
Server: cloudflare
Security headers present
Content-Security-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 4239819d399860eb27d8a73417f9bd108d45d11676f68b5edaae328ec197d55e
Saved response-header values · 17
Age
6884959
alt-svc
h3=":443"; ma=86400
CF-Cache-Status
HIT
CF-Ray
a50384217c5ccd97-GRU
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 19:09:31 GMT
Last-Modified
Fri, 23 Oct 2026 08:45:13 GMT
Server
cloudflare
surrogate-control
max-age=2147483647
surrogate-key
es-seguridad.webflow.io 68ee15040c7856c805cd817a pageId:68ee15050c7856c805cd81d3
Transfer-Encoding
chunked
Vary
accept-encoding
x-lambda-id
a86585ea-f1a3-4934-a603-afc1dec1e45e
x-wf-region
us-east-1

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

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

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

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. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:03:27.000000
    Evidence SHA-256
    9f003e04df21415df7f2c65e672d44abd46e86240e91b040b6508afc8a16b7c4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:03:27
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:03:27.000000
    Evidence SHA-256
    9f003e04df21415df7f2c65e672d44abd46e86240e91b040b6508afc8a16b7c4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:03:27
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:32.000000
    Evidence SHA-256
    72e3e8fdf9fb702cbbc6b4cdcee6fd579d2c75f563a69b2e3b307602660b58f7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:32
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:32.000000
    Evidence SHA-256
    72e3e8fdf9fb702cbbc6b4cdcee6fd579d2c75f563a69b2e3b307602660b58f7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:32
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:49.000000
    Evidence SHA-256
    8f1b9644a4bc2bc7c9a651d2d5307f0c6567061f1226561369fbff065f722012
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:49
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:49.000000
    Evidence SHA-256
    8f1b9644a4bc2bc7c9a651d2d5307f0c6567061f1226561369fbff065f722012
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:49
    Evidence reason
    alive_content
  7. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 20:25:16.000000
    Evidence SHA-256
    1b5564b16fc4633c6ebfc058db5643ad09022dbf9cc4d6a9eb6fc8e3d7533607
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 20:25:16
    Evidence reason
  8. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 20:25:16.000000
    Evidence SHA-256
    1b5564b16fc4633c6ebfc058db5643ad09022dbf9cc4d6a9eb6fc8e3d7533607
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 20:25:16
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    es-seguridad.webflow.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 94
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 16/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. VirusTotal

    16/92 engine detections

    View source
  2. Added to PhishDestroy

    es-seguridad.webflow.io

    View source
  3. URLScan

    Page captured

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

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.

es-seguridad.webflow.io

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid 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?

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

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 es-seguridad.webflow.io)
  • 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/es-seguridad.webflow.io"
  title="PhishDestroy threat report for es-seguridad.webflow.io"
  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>