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

custertell.weebly.com

In short

PhishDestroy stores a record for custertell.weebly.com. Source observations are dated separately; missing checks do not establish safety.

Review the evidence
Registrar
Square
Resolved IP
United States74.115.51.9WEEBLY - Weebly, Inc., US · CDN
Registered
Mar 29, 2006
First observed
Oct 25, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Reachable · access restricted Reachable response; page content was not verified Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Last known active
VirusTotal
17 / 92
engine detections ·
Page captures
2
open gallery
Domain age
7,522 days
registered 2006-03-29 according to RDAP
Oct 25, 2026 CDN
X Telegram API

Questions about custertell.weebly.com

Is custertell.weebly.com legit?

PhishDestroy stores a record for custertell.weebly.com. Source observations are dated separately; missing checks do not establish safety.

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

This report does not record which wallet requests custertell.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 custertell.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

Source evidenceVirusTotal 17 / 92 6 sources

VirusTotal

17 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 5004a75bfd26af28b1da83f61102ba8fce16ecd6575bf6490678e9b2bc85a190

Open report
Separate monitor record · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1714d-8183-71bb-a48d-4a6cb9e06c4c
score
0
malicious
false
result_at
2026-10-25T04:30:43Z
enriched_at
2026-10-25T09:11:42Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:43","urlscan_enriched_at":"2026-10-25 10:11:42"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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-10-25T07:20:21Z

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-10-25T07:20:21Z
source_timestamp
2026-10-25 08:20:21
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded
StateStored capture
Position1 / 2
Open capture Wayback Download
All capture links and hashes (2)
custertell.weebly.com: caution — 17/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card custertell.weebly.com: caution — 17/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v fbb17d4c8761

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context United States74.115.51.9 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 - Weebly, Inc., US · AS27647
Registration (base domain)weebly.com · Created Mar 29, 2006
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 15/100
Submitted URLhttp://custertell.weebly.com/
Observed page title
Even geduld...
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 64 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States74.115.51.9
Network ASN
AS27647
Organization
WEEBLY - Weebly, Inc., US
Observed location
United StatesUS
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-06 19:46:48
Valid until
2027-01-04 19:46:47
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-25 05:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint0ab63db1f470cfa51bc6372a78a47a8db5f315e8e14c970970e78d8f6ccd9281
Certificate names · 1 SAN
  • 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.9rapiddns.io

Latest Classified Outcome 2026-11-01 02:53:59 UTC

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

Technical details
Primary outcome Reachable but protected reason: Captcha 85% confidence
Attribution mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected Captcha Challenge 85% 2026-11-01 02:53:59 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:08:55 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

17 / 92 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
SafeToOpen
SOCRadar
Sophos
VIPRE
Webroot
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: 9 SHA-256 hashes: 6 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-10-29 01:58 UTC.

Open this scan on URLScan 01a1714d-8183-71bb-a48d-4a6cb9e06c4c ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Even geduld...
Crawler
Home
custertell.weebly.com
Stored observation history5

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

    captcha · challenge

  2. Availability monitor · Recorded state

    protected

    captcha · challenge

  3. Availability monitor · Recorded state

    protected

    captcha · challenge

  4. Availability monitor · Recorded state

    protected

    captcha · challenge

  5. Domain monitor · First collection record

    Reachable

All retained availability observations33

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
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-01 03:53:59.000000
    Evidence SHA-256
    501d95076207be45f734b14fb76a938e62f197d8197a77af35deb2f9813f594c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:53:59
    Evidence reason
    captcha
  2. 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-01 03:53:59.000000
    Evidence SHA-256
    501d95076207be45f734b14fb76a938e62f197d8197a77af35deb2f9813f594c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:53:59
    Evidence reason
    captcha
  3. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-01 00:08:55.000000
    Evidence SHA-256
    e2441b3f36e4f01a06cb9e29fe244ec7cbbdb9b8fc00c69a0e02eb202d92847c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:55
    Evidence reason
    captcha
  4. 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-01 00:08:55.000000
    Evidence SHA-256
    e2441b3f36e4f01a06cb9e29fe244ec7cbbdb9b8fc00c69a0e02eb202d92847c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:55
    Evidence reason
    captcha
  5. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-31 12:09:34.000000
    Evidence SHA-256
    e5e653dd96e6c6657cefd9ef0de7838c619c5ecabff6100e11c096adfc4b1d79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:34
    Evidence reason
    captcha
  6. 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-10-31 12:09:34.000000
    Evidence SHA-256
    e5e653dd96e6c6657cefd9ef0de7838c619c5ecabff6100e11c096adfc4b1d79
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:34
    Evidence reason
    captcha
  7. 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-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  8. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-31 03:30:41.000000
    Evidence SHA-256
    b3b2288680645bd1540745b8c13ada0f6c2cf323cf2987ef25a4f268bfdf7313
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:41
    Evidence reason
    captcha
  9. 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-10-31 03:30:41.000000
    Evidence SHA-256
    b3b2288680645bd1540745b8c13ada0f6c2cf323cf2987ef25a4f268bfdf7313
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:41
    Evidence reason
    captcha
  10. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-30 12:06:57.000000
    Evidence SHA-256
    e0e1c98adf709b3319accc1716976c8b52ef04cd91c4a6b6eb54ce83661eac66
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:57
    Evidence reason
    captcha
  11. 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-10-30 12:06:57.000000
    Evidence SHA-256
    e0e1c98adf709b3319accc1716976c8b52ef04cd91c4a6b6eb54ce83661eac66
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:57
    Evidence reason
    captcha
  12. 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-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  13. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-30 00:07:15.000000
    Evidence SHA-256
    225ab5b39372e7db7221596d61d725253bfe08ab6bc566c8334b5528e63882a1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:15
    Evidence reason
    captcha
  14. 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-10-30 00:07:15.000000
    Evidence SHA-256
    225ab5b39372e7db7221596d61d725253bfe08ab6bc566c8334b5528e63882a1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:15
    Evidence reason
    captcha
  15. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-29 12:07:34.000000
    Evidence SHA-256
    2a2956f4396acd2165a0e169f139fc94cd4813cc9e914535e04c7fd4eb878266
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:34
    Evidence reason
    captcha
  16. 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-10-29 12:07:34.000000
    Evidence SHA-256
    2a2956f4396acd2165a0e169f139fc94cd4813cc9e914535e04c7fd4eb878266
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:34
    Evidence reason
    captcha
  17. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-29 03:35:46.000000
    Evidence SHA-256
    d08e05fd862947b5c7b0b899a8bab355c0cf876d8a0a6972735924e0a40c8682
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:35:46
    Evidence reason
    captcha
  18. 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-10-29 03:35:46.000000
    Evidence SHA-256
    d08e05fd862947b5c7b0b899a8bab355c0cf876d8a0a6972735924e0a40c8682
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:35:46
    Evidence reason
    captcha
  19. 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-10-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  20. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-10-28 12:01:47.000000
    Evidence SHA-256
    5dc8a351198ddb94c90baaff3773038e68b803216323f79d69aaa58925261f91
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:47
    Evidence reason
    captcha
  21. 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-10-28 12:01:47.000000
    Evidence SHA-256
    5dc8a351198ddb94c90baaff3773038e68b803216323f79d69aaa58925261f91
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:47
    Evidence reason
    captcha
  22. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    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-10-28 00:02:16.000000
    Evidence SHA-256
    a4e5af526538bc5e474cee6a9d602faae75b6e01fa2ef695496aef73de1c60a8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:02:16
    Evidence reason
    captcha
  23. 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-10-28 00:02:16.000000
    Evidence SHA-256
    a4e5af526538bc5e474cee6a9d602faae75b6e01fa2ef695496aef73de1c60a8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:02:16
    Evidence reason
    captcha
  24. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    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-10-27 12:02:24.000000
    Evidence SHA-256
    e7c89c0cf5672c04f57b83d81f95bfb8c2eee6b29150a4d41d31529fb8bec62a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:24
    Evidence reason
    captcha
  25. 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-10-27 12:02:24.000000
    Evidence SHA-256
    e7c89c0cf5672c04f57b83d81f95bfb8c2eee6b29150a4d41d31529fb8bec62a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:24
    Evidence reason
    captcha
  26. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    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-10-26 13:02:17.000000
    Evidence SHA-256
    8dbb62a83d0ba2424922459a0a4eeb6f6dfaa58e0c4b11277ef4bd709ed128d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:17
    Evidence reason
    captcha
  27. 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-10-26 13:02:17.000000
    Evidence SHA-256
    8dbb62a83d0ba2424922459a0a4eeb6f6dfaa58e0c4b11277ef4bd709ed128d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:17
    Evidence reason
    captcha
  28. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    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-10-26 01:19:17.000000
    Evidence SHA-256
    6cc04cda3f2ec928164ebaf21676968feb119a7d83b0e683ed4d3d3f0c47ea9b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:17
    Evidence reason
    captcha
  29. 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-10-26 01:19:17.000000
    Evidence SHA-256
    6cc04cda3f2ec928164ebaf21676968feb119a7d83b0e683ed4d3d3f0c47ea9b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:17
    Evidence reason
    captcha
  30. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    captcha
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    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-10-25 13:22:50.000000
    Evidence SHA-256
    0e4e9da428a8f23291f3f8498e857cf9d60b60bee37e1089bd70ba025b320324
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:50
    Evidence reason
    captcha
  31. 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-10-25 13:22:50.000000
    Evidence SHA-256
    0e4e9da428a8f23291f3f8498e857cf9d60b60bee37e1089bd70ba025b320324
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:50
    Evidence reason
    captcha
  32. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:25:17.000000
    Evidence SHA-256
    a41b59a4a07b1c84c6a3edb3e34cf4023d720f58ad91f7d554764f152a0cd4ba
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 05:25:17
    Evidence reason
  33. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:25:17.000000
    Evidence SHA-256
    a41b59a4a07b1c84c6a3edb3e34cf4023d720f58ad91f7d554764f152a0cd4ba
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 05:25:17
    Evidence reason

Threat Response Pipeline

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

Recorded events: 6. 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
    custertell.weebly.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 4 of 4
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • VirusTotal
    Detections recorded on VirusTotal: 17/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

3 entries
  1. VirusTotal

    17/92 engine detections

    View source
  2. Added to PhishDestroy

    custertell.weebly.com

    View source
  3. URLScan

    Page captured

    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

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch 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 custertell.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.

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/custertell.weebly.com"
  title="PhishDestroy threat report for custertell.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>