Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 15/92 engines flagged. malicious: 15. suspicious: 0. Analysis time (as stored): 2026-11-01T17:43:50Z. Retrieved (as stored): 2026-11-04T21:22:05Z. Listed by external blocklists: PhishFeed. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
seczimbrupdate.weebly.com favicon

seczimbrupdate.weebly.com

In short

On 2026-09-27, seczimbrupdate.weebly.com displayed a page headed "Zimbra Security Update". The text addresses "Dear Customer," stating that different computers logged on to a Zimbra account with multiple password failures, and asks the visitor to verify information to avoid indefinite account suspension. It is signed "Zimbra Security Update."

“ZIMBRA UPDATE - Home”

Review the evidence
Registrar
Square
Resolved IP
United States74.115.51.8Weebly, Inc. · CDN
Registered
Mar 29, 2006
First observed
Nov 4, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Reachable · access restricted Reachable response; page content was not verified Observed HTTP probe
Risk signals
VirusTotal detections: 15/92 Stored blocklist matches: 1 Last known active
VirusTotal
15 / 92
engine detections ·
Blocklist matches
1
PhishFeed
URLScan
Malicious
engine verdict · score 86
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
7,529 days
registered 2006-03-29 according to RDAP · source data differ
Nov 4, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded seczimbrupdate.weebly.com on 2026-11-04. Stored VirusTotal result: 15/92 engines flagged. malicious: 15. suspicious: 0. Analysis time (as stored): 2026-11-01T17:43:50Z. Retrieved (as stored): 2026-11-04T21:22:05Z. Listed by external blocklists: PhishFeed. Risk: critical (95/100). Registrar: Square. Status: Reachable · access restricted. Hosting: Weebly, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
15 / 92
Blocklist matches
1
Hosting
United States74.115.51.8Weebly, Inc. · CDN
Registrar
Square
Registered
Mar 29, 2006
Page captures
8
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-09-27T08:08:46Z
SHA-256: 9a636027e430de0527908d6bf4a6fab6ca0b8748f47246e2adbe01bb4fd490b5

PhishDestroy analysis, reviewed version

On 2026-09-27, seczimbrupdate.weebly.com displayed a page headed "Zimbra Security Update". The text addresses "Dear Customer," stating that different computers logged on to a Zimbra account with multiple password failures, and asks the visitor to verify information to avoid indefinite account suspension. It is signed "Zimbra Security Update."

Below the message, a form marked "* INDICATES REQUIRED FIELD" provides fields for EMAIL, USERNAME, PA$$WORD, CONFIRM PA$$WORD and TELEPHONE, each with an asterisk, followed by an "UPDATE" button. A small blue logo appears at the top left, and a "POWERED BY weebly" banner sits at the bottom of the page.

Source evidenceVirusTotal 15 / 92 8 sources

VirusTotal

15 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
15
Suspicious
0
Undetected
32

Vendor labels

ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
SOCRadar
phishing
LevelBlue
phishing
Gridinsoft
phishing
ADMINUSLabs
malicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    74.115.51.8
  • TTL, seconds
    3600
    Type
    A
    Value
    74.115.51.9

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • *.weebly.com
  • weebly.com
Issuer
Let's Encrypt / YE2
Serial
537be20737256ed93d00e736e0c91ccf99d
SHA-256
0ab63db1f470cfa51bc6372a78a47a8db5f315e8e14c970970e78d8f6ccd9281
Subject
weebly.com
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 15,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "SOCRadar": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2006-03-29T00:00:00Z
Updated
2026-03-30T00:00:00Z
First seen
2025-03-03T05:37:05Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "74.115.51.8"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "74.115.51.9"
    }
]
Dns at
2026-11-01T20:03:03Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "*.weebly.com",
        "weebly.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "537be20737256ed93d00e736e0c91ccf99d",
    "sha256": "0ab63db1f470cfa51bc6372a78a47a8db5f315e8e14c970970e78d8f6ccd9281",
    "subject": "weebly.com",
    "valid_to": "2027-01-04T19:46:47Z",
    "valid_from": "2026-10-06T19:46:48Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
15
denominator
92
malicious
null
suspicious
null
vendors
["ADMINUSLabs","alphaMountain.ai","BitDefender","Chong Lua Dao","CyRadar","ESET","Forcepoint ThreatSeeker","G-Data","Gridinsoft","LevelBlue","Lionic","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-11-01 17:43:50
checked_at
2026-11-04 22:22:15
fetched_at
2026-11-04 21:22:15
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

b49b01c1-22d3-4ecb-a335-01615a8bdd38

Final URL

https://seczimbrupdate.weebly.com/

HTTP response

200

Navigation history

  • URL
    https://seczimbrupdate.weebly.com/
    Status
    200

DOM structure hash

d279d6f99d57f0600439a003c667c25c25dfab4f5dc9e597375cfc6b8c5a5896

Document hash

b2d1335cbfc24d8e8acb08b716b31fb1689d5228d09bdd3ff90c28ea7adf9cc9

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    seczimbrupdate.weebly.com
    Type
    A
    Value
    74.115.51.9
  • Name
    seczimbrupdate.weebly.com
    Type
    A
    Value
    74.115.51.8

DNSSEC valid

No

IP address

127.0.1.22

127.0.1.22 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns-123.awsdns-15.com
  • ns-1500.awsdns-59.org
  • ns-1797.awsdns-32.co.uk
  • ns-646.awsdns-16.net
Original source fields · JSON
Uuid
b49b01c1-22d3-4ecb-a335-01615a8bdd38
Final url
https://seczimbrupdate.weebly.com/
Status
200
History
[
    {
        "url": "https://seczimbrupdate.weebly.com/",
        "status": 200
    }
]
DOM structure hash
d279d6f99d57f0600439a003c667c25c25dfab4f5dc9e597375cfc6b8c5a5896
Document hash
b2d1335cbfc24d8e8acb08b716b31fb1689d5228d09bdd3ff90c28ea7adf9cc9
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "seczimbrupdate.weebly.com",
        "type": "A",
        "value": "74.115.51.9"
    },
    {
        "name": "seczimbrupdate.weebly.com",
        "type": "A",
        "value": "74.115.51.8"
    }
]
Dnssec valid
false
Ip
127.0.1.22

127.0.1.22 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2006-03-29T00:25:07Z",
    "updated": "2026-08-10T19:04:53Z",
    "expires": "2032-03-28T23:25:07Z",
    "nameservers": [
        "ns-123.awsdns-15.com",
        "ns-1500.awsdns-59.org",
        "ns-1797.awsdns-32.co.uk",
        "ns-646.awsdns-16.net"
    ]
}

URLScan

Malicious · engine verdict · score 86

SHA-256 88de1166efef08c317c234711c11aad7043fcc8977717d1fddf85f5564e3183b

Open report
URLScanOriginal source recordObserved: 25 fields

Observed: · Retrieved:

Report ID

01a1a8e9-3a0f-75e2-8d4f-a708566858d2

Final URL

https://seczimbrupdate.weebly.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://seczimbrupdate.weebly.com/
    From
    http://seczimbrupdate.weebly.com/
    Status
    307

IP address

74.115.51.8

Reverse DNS (PTR)

wildcard.weebly.com

Contacted domains

  • cdn2.editmysite.com
  • cdn11.editmysite.com
  • ec.editmysite.com
  • www.gstatic.com
  • www.google.com
  • cdn3.editmysite.com

Contacted IP addresses

  • 172.253.115.94
  • 32.185.215.106
  • 142.251.153.119
  • 151.101.65.46
  • 74.115.51.8

Autonomous systems (ASN)

  • 15169
  • 16509
  • 54113
  • 27647

Server countries

  • US

Linked domains

  • www.weebly.com

Document hash

b2d1335cbfc24d8e8acb08b716b31fb1689d5228d09bdd3ff90c28ea7adf9cc9

Script hashes

  • 5a630b41e7c3d34392bcb150a5731b6261bc6314d71d5db8407a646af15bf8af
  • b6353ca52760aba4e7547ae9861db68158dc2af0f4febece55e5c775ee4449f5
  • 0567021bc3973d113c6b0b6e68d0e9a8b53f38a7f60716c83214a133cc00139a

JavaScript globals

  • Weebly
  • STATIC_BASE
  • ASSETS_BASE
  • STYLE_PREFIX
  • $
  • jQuery
  • _W
  • publishedWBJP
  • RECAPTCHA_PUBLIC_KEY
  • INVISIBLE_RECAPTCHA_PUBLIC_KEY
  • _
  • Mustache
  • jQBrowser
  • PlatformElement
  • whenThemeCSSLoaded
  • isThemeCSSLoaded
  • blogCommentDisplayForm
  • YTPlayer
  • VimeoPlayer
  • Sd
  • Rd
  • Cd
  • videojs
  • _V_
  • jsonrpc
  • getCartCount
  • getCartNavElement
  • reportCartNavElement
  • initPublishedFlyoutMenus
  • flyoutMenusRefreshable
  • initEditorFlyoutMenus
  • refreshNavCondense
  • disableFlyouts
  • FlyoutMenu
  • objectify
  • mejs
  • MediaElement
  • MediaElementPlayer
  • require
  • platformElementRequire

Cookies

  • __cf_bm
  • _snow_ses.fd57
  • _snow_id.fd57
  • sp

Browser storage keys

  • modernizr
  • snowplowOutQueue_snowday__wn_post2

TLS session and certificate

Subject alternative names
  • *.weebly.com
  • weebly.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
weebly.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

611

Differs from the registration date in RDAP (2006-03-29), which gives 7525 days on the scan date 2026-11-04. The two sources disagree; both values are kept as recorded.

Registered domain age, days

4971

Differs from the registration date in RDAP (2006-03-29), which gives 7525 days on the scan date 2026-11-04. The two sources disagree; both values are kept as recorded.

Certificate age, days

29

Certificate validity, days

89

Page requests

34

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
86
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1a8e9-3a0f-75e2-8d4f-a708566858d2
Final url
https://seczimbrupdate.weebly.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://seczimbrupdate.weebly.com/",
        "from": "http://seczimbrupdate.weebly.com/",
        "status": 307
    }
]
Ip
74.115.51.8
Ptr
wildcard.weebly.com
Contacted domains
[
    "cdn2.editmysite.com",
    "cdn11.editmysite.com",
    "ec.editmysite.com",
    "www.gstatic.com",
    "www.google.com",
    "cdn3.editmysite.com"
]
Contacted IP addresses
[
    "172.253.115.94",
    "32.185.215.106",
    "142.251.153.119",
    "151.101.65.46",
    "74.115.51.8"
]
Asns
[
    "15169",
    "16509",
    "54113",
    "27647"
]
Countries
[
    "US"
]
Linked domains
[
    "www.weebly.com"
]
Document hash
b2d1335cbfc24d8e8acb08b716b31fb1689d5228d09bdd3ff90c28ea7adf9cc9
Script hashes
[
    "5a630b41e7c3d34392bcb150a5731b6261bc6314d71d5db8407a646af15bf8af",
    "b6353ca52760aba4e7547ae9861db68158dc2af0f4febece55e5c775ee4449f5",
    "0567021bc3973d113c6b0b6e68d0e9a8b53f38a7f60716c83214a133cc00139a"
]
Globals
[
    "Weebly",
    "STATIC_BASE",
    "ASSETS_BASE",
    "STYLE_PREFIX",
    "$",
    "jQuery",
    "_W",
    "publishedWBJP",
    "RECAPTCHA_PUBLIC_KEY",
    "INVISIBLE_RECAPTCHA_PUBLIC_KEY",
    "_",
    "Mustache",
    "jQBrowser",
    "PlatformElement",
    "whenThemeCSSLoaded",
    "isThemeCSSLoaded",
    "blogCommentDisplayForm",
    "YTPlayer",
    "VimeoPlayer",
    "Sd",
    "Rd",
    "Cd",
    "videojs",
    "_V_",
    "jsonrpc",
    "getCartCount",
    "getCartNavElement",
    "reportCartNavElement",
    "initPublishedFlyoutMenus",
    "flyoutMenusRefreshable",
    "initEditorFlyoutMenus",
    "refreshNavCondense",
    "disableFlyouts",
    "FlyoutMenu",
    "objectify",
    "mejs",
    "MediaElement",
    "MediaElementPlayer",
    "require",
    "platformElementRequire"
]
Cookies
[
    "__cf_bm",
    "_snow_ses.fd57",
    "_snow_id.fd57",
    "sp"
]
Storage keys
[
    "modernizr",
    "snowplowOutQueue_snowday__wn_post2"
]
Tls
{
    "san": [
        "*.weebly.com",
        "weebly.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "weebly.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-04T19:46:47Z",
    "valid_from": "2026-10-06T19:46:48Z"
}
Domain age days
611

Differs from the registration date in RDAP (2006-03-29), which gives 7525 days on the scan date 2026-11-04. The two sources disagree; both values are kept as recorded.

Apex age days
4971

Differs from the registration date in RDAP (2006-03-29), which gives 7525 days on the scan date 2026-11-04. The two sources disagree; both values are kept as recorded.

Tls age days
29
Tls valid days
89
Requests
34
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 86,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "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
01a0e1e8-b387-75ce-ace5-990faf010081
score
null
malicious
null
result_at
null
enriched_at
2026-11-07T09:16:35Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-07 10:16:35"}
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

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

Open report
Separate monitor score · 15 / 100 · 2026-11-04T21:24:02Z

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
15
analyzed_at
2026-11-04T21:24:02Z
source_timestamp
2026-11-04 22:24:02
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
seczimbrupdate.weebly.com: Recorded Zimbra Security Update form page
ai_description
PhishDestroy records seczimbrupdate.weebly.com as a page titled Zimbra Security Update, presenting a form requesting email, username, password and telephone details.
ai_summary
On 2026-09-27, seczimbrupdate.weebly.com displayed a page headed "Zimbra Security Update". The text addresses "Dear Customer," stating that different computers logged on to a Zimbra account with multiple password failures, and asks the visitor to verify information to avoid indefinite account suspension. It is signed "Zimbra Security Update." Below the message, a form marked "* INDICATES REQUIRED FIELD" provides fields for EMAIL, USERNAME, PA$$WORD, CONFIRM PA$$WORD and TELEPHONE, each with an asterisk, followed by an "UPDATE" button. A small blue logo appears at the top left, and a "POWERED BY weebly" banner sits at the bottom of the page.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-04 21:32:45
revision
2f08658e6f5686d24379e1128c90cc3eb9f35a84acab65fcdf35eb76ceedc7ed
mode
reviewed
interpretation
Selected public package; text generation time is separate from source 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: 25 fields

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

User agents
  • NerdyBot
  • dotbot
  • *
Present
Yes
Sitemap URLs
  • https://seczimbrupdate.weebly.com/sitemap.xml

Sitemap

Present
Yes
URL count
1

Page title and metadata

Open Graph URL
https://seczimbrupdate.weebly.com/
Page title
ZIMBRA UPDATE - Home
Open Graph image
https://seczimbrupdate.weebly.com/uploads/1/4/8/2/148251328/zimbralog.png
Open Graph title
ZIMBRA UPDATE
Open Graph site name
ZIMBRA UPDATE
Open Graph description
ZIMBRA UPDATE

Trackers

Requests
40
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Snowplow
    Company
    Snowplow Analytics
    Country
    GB
    Category
    Site Analytics
    Requests
    1
  • Name
    Google Recaptcha
    Company
    Google
    Country
    US
    Category
    Utilities
    Requests
    2

Forms and mixed content

Scripts without SRI
  • https://cdn2.editmysite.com/js/lang/en/stl.js
  • https://cdn2.editmysite.com/js/site/main.js
  • https://cdn11.editmysite.com/js/site/footerSignup.js
  • https://cdn2.editmysite.com/js/site/main-customer-accounts-site.js
  • https://cdn2.editmysite.com/js/jquery-1.8.3.min.js
Third-party scripts
5

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
19
TLS
18
Waiting
220
Connection
20
Download
1
Response time, ms
278

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
29802
CO₂, grams
0.0011
Cleaner than, %
48

DNS servers

Nameservers
  • IP address
    205.251.192.123
    Host
    ns-123.awsdns-15.com
  • IP address
    205.251.199.5
    Host
    ns-1797.awsdns-32.co.uk
  • IP address
    205.251.197.220
    Host
    ns-1500.awsdns-59.org
  • IP address
    205.251.194.134
    Host
    ns-646.awsdns-16.net
DNS zone
weebly.com

Cookies

Cookies
  • Name
    __cf_bm
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    _snow_ses.fd57
  • Name
    _snow_id.fd57

Location

IP address
74.115.51.9
ASN
27647
Organization
Weebly, Inc.
City
Oakland
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
weebly.com

DNS records

A
  • 74.115.51.8
  • 74.115.51.9

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
74.115.51.8
IP version
4

Redirects

Redirect chain
  • https://seczimbrupdate.weebly.com

Subdomains

Count
25
Subdomains
  • admin.promote.weebly.com
  • api.weebly.com
  • cdn-promote.weebly.com
  • checkout.weebly.com
  • click.promote.weebly.com
  • cloud-designer.weebly.com
  • cloud-developer.weebly.com
  • content-promote.weebly.com
  • designers.weebly.com
  • dev.weebly.com
  • domains.weebly.com
  • ec.weebly.com
  • fallback.weebly.com
  • help-designers.weebly.com
  • images.weebly.com
  • mobileapi.weebly.com
  • namecheap-connector.weebly.com
  • p.weebly.com
  • promote.weebly.com
  • sandbox.weebly.com
  • static-cdn.weebly.com
  • static-promote.weebly.com
  • videos.weebly.com
  • www-alt.weebly.com
  • www.weebly.com

Page links

External link addresses
  • https://www.weebly.com/signup
External links
1
Internal links
2

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • clientUpdateProhibited https://icann.org/epp
Nameservers
  • ns-123.awsdns-15.com
  • ns-1500.awsdns-59.org
  • ns-1797.awsdns-32.co.uk
  • ns-646.awsdns-16.net

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "agents": [
        "NerdyBot",
        "dotbot",
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://seczimbrupdate.weebly.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 1
}
Page title and metadata
{
    "ogUrl": "https://seczimbrupdate.weebly.com/",
    "title": "ZIMBRA UPDATE - Home",
    "ogImage": "https://seczimbrupdate.weebly.com/uploads/1/4/8/2/148251328/zimbralog.png",
    "ogTitle": "ZIMBRA UPDATE",
    "ogSiteName": "ZIMBRA UPDATE",
    "ogDescription": "ZIMBRA UPDATE"
}
Trackers
{
    "requests": 40,
    "trackers": [
        {
            "name": "Google",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Snowplow",
            "company": "Snowplow Analytics",
            "country": "GB",
            "category": "Site Analytics",
            "requests": 1
        },
        {
            "name": "Google Recaptcha",
            "company": "Google",
            "country": "US",
            "category": "Utilities",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn2.editmysite.com/js/lang/en/stl.js",
        "https://cdn2.editmysite.com/js/site/main.js",
        "https://cdn11.editmysite.com/js/site/footerSignup.js",
        "https://cdn2.editmysite.com/js/site/main-customer-accounts-site.js",
        "https://cdn2.editmysite.com/js/jquery-1.8.3.min.js"
    ],
    "third_party_scripts": 5
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 19,
        "tls": 18,
        "wait": 220,
        "connect": 20,
        "download": 1
    },
    "response_ms": 278
}
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": 29802,
    "co2_grams": 0.0011,
    "cleaner_than": 48
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.192.123",
            "host": "ns-123.awsdns-15.com"
        },
        {
            "ip": "205.251.199.5",
            "host": "ns-1797.awsdns-32.co.uk"
        },
        {
            "ip": "205.251.197.220",
            "host": "ns-1500.awsdns-59.org"
        },
        {
            "ip": "205.251.194.134",
            "host": "ns-646.awsdns-16.net"
        }
    ],
    "zone": "weebly.com"
}
Cookies
{
    "cookies": [
        {
            "name": "__cf_bm",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "_snow_ses.fd57"
        },
        {
            "name": "_snow_id.fd57"
        }
    ]
}
Location
{
    "ip": "74.115.51.9",
    "asn": "27647",
    "org": "Weebly, Inc.",
    "city": "Oakland",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "weebly.com"
}
DNS records
{
    "A": [
        "74.115.51.8",
        "74.115.51.9"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "74.115.51.8",
    "family": 4
}
Redirects
{
    "chain": [
        "https://seczimbrupdate.weebly.com"
    ]
}
Subdomains
{
    "count": 25,
    "subdomains": [
        "admin.promote.weebly.com",
        "api.weebly.com",
        "cdn-promote.weebly.com",
        "checkout.weebly.com",
        "click.promote.weebly.com",
        "cloud-designer.weebly.com",
        "cloud-developer.weebly.com",
        "content-promote.weebly.com",
        "designers.weebly.com",
        "dev.weebly.com",
        "domains.weebly.com",
        "ec.weebly.com",
        "fallback.weebly.com",
        "help-designers.weebly.com",
        "images.weebly.com",
        "mobileapi.weebly.com",
        "namecheap-connector.weebly.com",
        "p.weebly.com",
        "promote.weebly.com",
        "sandbox.weebly.com",
        "static-cdn.weebly.com",
        "static-promote.weebly.com",
        "videos.weebly.com",
        "www-alt.weebly.com",
        "www.weebly.com"
    ]
}
Page links
{
    "external": [
        "https://www.weebly.com/signup"
    ],
    "external_count": 1,
    "internal_count": 2
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2006-03-29T00:25:07Z",
    "updated": "2026-08-10T19:04:53Z",
    "expires": "2032-03-28T23:25:07Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns-123.awsdns-15.com",
        "ns-1500.awsdns-59.org",
        "ns-1797.awsdns-32.co.uk",
        "ns-646.awsdns-16.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats
View full Cloudflare Radar report

Questions about seczimbrupdate.weebly.com

Is seczimbrupdate.weebly.com legit?

PhishDestroy rates seczimbrupdate.weebly.com as critical risk (95/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 15/92 engines flagged. malicious: 15. suspicious: 0. Analysis time (as stored): 2026-11-01T17:43:50Z. Retrieved (as stored): 2026-11-04T21:22:05Z. Listed by external blocklists: PhishFeed. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is seczimbrupdate.weebly.com safe to connect a wallet?

This report does not record which wallet requests seczimbrupdate.weebly.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used seczimbrupdate.weebly.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Checked, no match

Last checked

Stored Capture · 8 captures

URLScan · 2026-09-27 1 / 8 Used in the analysis Source file SHA-256: 9a636027e430de0527908d6bf4a6fab6ca0b8748f47246e2adbe01bb4fd490b5 SHA-256 of the prepared copy given to the model: 362b22a5d0047d625cf3e61c949383af92572f31e0f1b4dff22d9f415d47f8f0
SourceURLScan · 2026-09-27
Recorded
StateStored capture
Final URLhttps://seczimbrupdate.weebly.com/
Position1 / 8
Open capture Source Report Wayback Download
All capture links and hashes (8)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 86 report ↗
IP Context United States74.115.51.8 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Square
Abuse contactweebly-abuse@squareup.com, abuse@squareup.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for weebly.com →
Hosting abuse contact weebly-abuse@squareup.com Weebly, Inc. · AS27647
Registration (base domain)weebly.com · Created Mar 29, 2006
WHOIS statusclientDeleteProhibitedclientTransferProhibitedclientUpdateProhibited
HTTP Status403 Forbidden
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
DOM Analysisanalyzed Nov 4, 2026score 15/100
Submitted URLhttp://seczimbrupdate.weebly.com/
Observed page title
ZIMBRA UPDATE - Home
TLS Certificate
Issued by YE2

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States74.115.51.8
Network ASN
AS27647
AS name
WEEBLY - Weebly, Inc., US
Organization
Weebly, Inc.
Observed location
United StatesOakland, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-08-08 20:20:54
Valid until
2026-11-06 20:20:53
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint0ab63db1f470cfa51bc6372a78a47a8db5f315e8e14c970970e78d8f6ccd9281
Certificate names · 2 SANs
  • *.weebly.com
  • weebly.com

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

viewdns.info · 74.115.51.8rapiddns.io

Latest Classified Outcome 2026-11-07 23:52:24 UTC

The site was reachable but behind an access challenge at the latest check.

Technical details
Primary outcome Reachable but protected reason: Cloudflare Challenge 85% confidence
Attribution Cloudflare mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected Cloudflare Challenge Cloudflare Challenge 85% 2026-11-07 23:52:24 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 11:50:20 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
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
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
SOCRadar
LevelBlue
Gridinsoft
ADMINUSLabs
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of seczimbrupdate.weebly.com · checked Nov 4, 2026

87
Needs Work
Performance
FCP
2.98 s
First Contentful Paint
LCP
2.98 s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
101 ms
Total Blocking Time
SI
4.11 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://seczimbrupdate.weebly.com/
Final URL: https://seczimbrupdate.weebly.com/
ZIMBRA UPDATE - Home
Response
HTTP 200
HTML body
29.1 KB
Compressed
7.3 KB
Links
5 internal · 1 external
Detected technologies
cloudflarebootstrapjquery
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Cache-Status: EXPIRED
Cache-Control: max-age=30, private, no-store
Server: cloudflare
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 40a2146151863bcf46c786d596e81a308d1b0d26d74635be441e92656f29b1b4
Open Graph title: ZIMBRA UPDATE
Open Graph description: ZIMBRA UPDATE
Saved response-header values · 13
Cache-Control
max-age=30, private, no-store
cdn-cache-control
max-age=30, public
CF-Cache-Status
EXPIRED
CF-Ray
a556a2c7adcac595-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Wed, 04 Nov 2026 21:15:45 GMT
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding,User-Agent
X-Host
grn14.sf2p.intern.weebly.net
X-UA-Compatible
IE=edge,chrome=1

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

Archived
Registration & observation details2

Availability observations

Last reachable 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.

Captured network requests

Network requests: 34 SHA-256 hashes: 33 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-04 23:39 UTC.

Open this scan on URLScan 01a1a8e9-3a0f-75e2-8d4f-a708566858d2 ↗

Stored observation history3

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

    protected

    cloudflare_challenge · Cloudflare · challenge

  2. Availability monitor · Recorded state

    protected

    cloudflare_challenge · Cloudflare · challenge

  3. Availability monitor · Recorded state

    protected

    captcha · challenge

All retained availability observations15

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_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:52:24.000000
    Evidence SHA-256
    2401c57a639d4f37bc71094cc63ec26b3703d0c4a55105deff38e12edece65c2
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-08 00:52:24
    Evidence reason
    cloudflare_challenge
  2. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:52:24.000000
    Evidence SHA-256
    2401c57a639d4f37bc71094cc63ec26b3703d0c4a55105deff38e12edece65c2
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-08 00:52:24
    Evidence reason
    cloudflare_challenge
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-07 23:22:04.326583
    Evidence SHA-256
    19ed99e260d67463304cd035997394a09991119b8c1f635f2967c41ae291fdce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 23:22:04.326583
    Evidence reason
  4. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:50:20.000000
    Evidence SHA-256
    1c385b334e81cbb36a7f10e1c543addc343f1661f531dc0669ca26cd0b1e4cd6
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-07 12:50:20
    Evidence reason
    cloudflare_challenge
  5. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:50:20.000000
    Evidence SHA-256
    1c385b334e81cbb36a7f10e1c543addc343f1661f531dc0669ca26cd0b1e4cd6
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-07 12:50:20
    Evidence reason
    cloudflare_challenge
  6. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 04:37:25.000000
    Evidence SHA-256
    f38b4744103610b3d47890051cd1d72698431943f26cb522f5c5d06ce115c190
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-07 04:37:25
    Evidence reason
    cloudflare_challenge
  7. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 04:37:25.000000
    Evidence SHA-256
    f38b4744103610b3d47890051cd1d72698431943f26cb522f5c5d06ce115c190
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-07 04:37:25
    Evidence reason
    cloudflare_challenge
  8. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:42:32.000000
    Evidence SHA-256
    2bc90667f658bd497f00e7f6bf83fc78d66c0913cde0a24deeac5583dcb9c9b3
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-07 00:42:32
    Evidence reason
    cloudflare_challenge
  9. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:42:32.000000
    Evidence SHA-256
    2bc90667f658bd497f00e7f6bf83fc78d66c0913cde0a24deeac5583dcb9c9b3
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-07 00:42:32
    Evidence reason
    cloudflare_challenge
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-06 23:21:40.556826
    Evidence SHA-256
    2071dfbc1c6ae55fbd72318bd0bd5b8ac6720ae3a22d4fd33ac3fef7bf7b47da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 23:21:40.556826
    Evidence reason
  11. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-05 23:21:20.401484
    Evidence SHA-256
    6561edb8793c530bd35b9930c0ef92bee67e8e1395a2c6e53ebfe984a32e4303
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 23:21:20.401484
    Evidence reason
  12. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    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-11-05 03:56:55.000000
    Evidence SHA-256
    0eb2ed56a0945a08b8f7d03b67406d61402f227c3726a2acb74fe04f2853c437
    Evidence timestamp as recorded
    2026-11-05 03:56:55
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  13. http_observationprotected
    Observation source
    http_observation
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:56:55.000000
    Evidence SHA-256
    3a7e2f8b37befc85f7e63edde23cb3880a93818f56b37fce4452e661a240ba45
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:56:55
    Evidence reason
    captcha
  14. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-04 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    Evidence reason
  15. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    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-11-04 20:20:44.992120
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 11. 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
    seczimbrupdate.weebly.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 86
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 15/92
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Phishing, Security threats
  • 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

5 entries
  1. URLScan

    Page captured

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    seczimbrupdate.weebly.com

    View source
  5. VirusTotal

    15/92 engine detections

    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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

seczimbrupdate.weebly.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Stored certificate expired or unverified CF Radar Malicious 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 Reachable · access restricted
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.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 seczimbrupdate.weebly.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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/seczimbrupdate.weebly.com"
  title="PhishDestroy threat report for seczimbrupdate.weebly.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>