Skip to security report
Domain security and threat intelligence
dhjcf.weebly.com favicon

dhjcf.weebly.com

In short

dhjcf.weebly.com is a Telstra impersonation page detected by PhishDestroy on 2026-09-11. Risk: critical (100/100). Registrar: Weebly. Status: Content unavailable. Hosting: WEEBLY - Weebly, Inc., US. VirusTotal: 17/89 engines flag it. Do not enter credentials or connect a wallet.

“Telstra”

Registrar
Weebly
Resolved IP
74.115.51.9
Registered
Mar 29, 2006
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 17/89 Automated brand label: Telstra
Sep 11, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 17 / 89 6 sources

VirusTotal

17 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing

Analysis

Critical
VirusTotal
17 / 89
Page captures
9

PhishDestroy threat report

Overview

dhjcf.weebly.com is a phishing page that posed as Telstra, Australia's largest telecom provider. It was titled simply "Telstra" and was aimed at the carrier's mobile, broadband and billing customers. PhishDestroy first flagged it on 2026-09-11. The site has been offline since 2026-09-21, and a recheck on 2026-10-19 found nothing left at the root.

How the scam works

Telstra-themed phishing usually starts with a text or email about an unpaid bill, a suspended service or a refund, and links the victim to a page that looks like Telstra's sign-in or payment screen. Anything typed there goes to the operator, not to Telstra. That can include the My Telstra login, card numbers or personal identity details. A stolen telco login is especially dangerous because it can be used to take over the account, port the phone number or intercept SMS one-time codes for other services.

Evidence

Seventeen of 89 VirusTotal engines flagged the page as of 2026-09-20. Those engines include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, Ermes and alphaMountain.ai. Agreement across that many independent vendors is strong for a short-lived page on a shared platform. urlscan.io returned a malicious verdict and its brand detection recognised Telstra on the page, which matches our classification. The site is listed on the PhishDestroy blocklist.

Infrastructure

The page was a free subdomain on the Weebly site builder, not a domain the operator registered. The 2006-03-29 registration date and the Weebly registrar both belong to the platform itself. Hosting sat on Weebly's own US network, and the Let's Encrypt certificate is the standard one Weebly issues to every site. The padlock therefore said nothing about legitimacy. Free builders like this let phishers launch quickly behind a trusted parent domain, which explains the roughly ten-day lifespan before the page went dark.

What to do

If you entered your Telstra login on this page, change that password immediately through Telstra's official app or website. Also change it on any other service where you reused it, and turn on two-factor authentication. If you gave card details, call your bank to cancel the card and dispute any charges you don't recognise. Ask Telstra to add a port-out or account PIN, and watch for sudden loss of mobile signal, which can signal a SIM swap. Defenders should block this specific subdomain rather than all of weebly.com, report future copies to Weebly's abuse team, and search mail and SMS logs for links to it.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-11T13:01:01Z

Observed: · Retrieved:

Uuid
01a0908e-85c9-74e5-84c1-7b359be0609e
Final url
https://dhjcf.weebly.com/
Status
200
Ip
74.115.51.9
Ptr
wildcard.weebly.com
Contacted domains
[
    "cdn2.editmysite.com",
    "cdn11.editmysite.com",
    "ec.editmysite.com",
    "www.gstatic.com",
    "www.google.com",
    "cdn3.editmysite.com",
    "ssl.google-analytics.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "2a00:1450:4001:c25::5e",
    "52.88.255.80",
    "2001:4860:482c:7700::",
    "2a00:1450:4001:c25::61",
    "2a04:4e42:600::302",
    "2a04:4e42::302",
    "2a00:1450:4001:c0f::5f",
    "74.115.51.9"
]
Asns
[
    "15169",
    "16509",
    "54113",
    "27647"
]
Countries
[
    "DE",
    "US"
]
Document hash
62ab47c01af2343195533bbf689ed72d6fbe2b2b61203a26c575926c9a90bb29
Script hashes
[
    "397452d9f6a2ea6a2135b45c9e40139c68ac6661f3bab4413e7299586ccb408a",
    "5a630b41e7c3d34392bcb150a5731b6261bc6314d71d5db8407a646af15bf8af",
    "b6353ca52760aba4e7547ae9861db68158dc2af0f4febece55e5c775ee4449f5",
    "f75570c56743e8c705cb06f5f1f9b1f8f2cc13119f5e2acda2f3bb8d987de94a",
    "446f48f512ecc0b771af3c21a3036de3a1c5740d1e6bdbb61448834326d0c738",
    "c4cd233d3d6b0f184e99d5017e521b4c6f9106d3e546864a8ba516189b934311",
    "cfbf67a85c039719090cff2c4718de99203b1ced78cfb8fae5f7240d2f1570b7"
]
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.33a4",
    "_snow_id.33a4",
    "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": "2026-11-06T20:20:53Z",
    "valid_from": "2026-08-08T20:20:54Z"
}
Domain age days
1
Apex age days
4917
Tls age days
33
Tls valid days
89
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "telstra"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Telstra"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}
Cloudflare Radar · 2026-09-11T17:11:06Z

Observed: · Retrieved:

Uuid
58c7242d-95cc-4c74-b819-558bd3d91cc6
Final url
https://dhjcf.weebly.com/
Status
200
History
[
    {
        "url": "https://dhjcf.weebly.com/",
        "status": 200
    }
]
DOM structure hash
a7c7f17cf3b540afe98a278e64c0cb05bfea92522b02ced52253d7b65f390330
Document hash
b8fd0b88369679265c6040f783db5eff2fba0f2555843910f1e93c6bf4a16931
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "dhjcf.weebly.com",
        "type": "A",
        "value": "74.115.51.9"
    },
    {
        "name": "dhjcf.weebly.com",
        "type": "A",
        "value": "74.115.51.8"
    }
]
Dnssec valid
false
Ip
74.115.51.9
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"
    ]
}
VirusTotal · 2026-10-12T11:29:05Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 16,
    "suspicious": 1,
    "undetected": 29
}
Vendor labels
{
    "ESET": "phishing",
    "Ermes": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "suspicious",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Created
2006-03-29T00:00:00Z
Updated
2026-03-30T00:00:00Z
First seen
2026-09-10T11:10:54Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "74.115.51.8"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "74.115.51.9"
    }
]
Dns at
2026-10-12T11:29:19Z
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"
}

Questions about dhjcf.weebly.com

Is dhjcf.weebly.com legit?

No. PhishDestroy classifies dhjcf.weebly.com as a Telstra impersonation page (risk: critical, 100/100); it was first detected on 2026-09-11. VirusTotal: 17/89 engines flag it. Treat the site as unsafe.

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

No. Do not connect a wallet, sign messages or approve tokens on dhjcf.weebly.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

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

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 9 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Telstra report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Weebly
Registration (base domain)weebly.com · Created Mar 29, 2006 — Expires Mar 28, 2032
HTTP Status404 Not Found
Time to First Unavailability 9 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
DOM Analysisanalyzed Sep 12, 2026score 93/1001 brand signal
Submitted URLhttp://dhjcf.weebly.com/
Favicon Hash
Observed page title
Telstra
Automated brand references
Telstra
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 13 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
74.115.51.9
Network ASN
AS27647
Organization
Weebly, Inc.
Observed location
Oakland, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 4

  • ns-123.awsdns-15.com
  • ns-1500.awsdns-59.org
  • ns-1797.awsdns-32.co.uk
  • ns-646.awsdns-16.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-08-08 20:20:54
Valid until
2026-11-06 20:20:53
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-11 22:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9f07f6a9d3d9a7e775e4fbb006342835f96f7bb95121877d4e458dfa52b48bfb
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.

Latest Classified Outcome 2026-10-23 01:26:13 UTC

Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-23 01:26:13 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-20 22:00:58 UTC current episode first observed: 2026-10-01 01:53:37 UTC observed RIP window: 2026-09-20 22:00:58 UTC → 2026-10-01 01:53:37 UTC · 243.88h midpoint estimate ≈ 2026-09-25 23:57:17 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 8 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 9 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of dhjcf.weebly.com · checked Sep 11, 2026

52
Needs Work
Performance
FCP
3.49s
First Contentful Paint
LCP
7.94s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
540ms
Total Blocking Time
SI
4.99s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

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

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

Check for cloaking

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

Page titles differ

http_other: raw=http_404; http=404; via=http_proxy; server=cloudflare

Browser
Telstra
Crawler
404 - Page Not Found
dhjcf.weebly.com
Saved result
Cloaked / Filtered
Stored observation history12

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

  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  6. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  7. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    17/89 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Added to PhishDestroy

    dhjcf.weebly.com

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including dhjcf.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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/dhjcf.weebly.com"
  title="PhishDestroy threat report for dhjcf.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>