On 2026-10-08, autoconfig.hsbccpersonalonlinebanking.com returned an HTTP 200 status code, indicating a successful web response on that date. Google Safe Browsing flagged the domain for social engineering, highlighting a potential security concern from a major source.
Recorded Evidence
VirusTotal reported 12 detections out of 92 scanners for this domain on 2026-10-07. The domain was listed on the Phishunt blocklist as of 2026-10-07. Google Safe Browsing flagged it for social engineering on 2026-10-08. The SSL certificate was issued by Let's Encrypt / YR1 and scanned on 2026-10-07. Phishdestroy also internally listed the domain, and it was first observed on 2026-10-07.
Interpretation
The records from VirusTotal, Google Safe Browsing, and Phishunt provide multiple perspectives on how autoconfig.hsbccpersonalonlinebanking.com was evaluated by security sources. These observations, each with specific dates and findings, allow for comparison of how the domain was treated by different monitoring services.
Recommended Actions
For autoconfig.hsbccpersonalonlinebanking.com, retain the dated records from VirusTotal, Google Safe Browsing, and Phishunt for ongoing review. Preserve the HTTP response and SSL scan details for technical analysis. Use these records to monitor and compare future observations from each source.
Certificate hostname mismatch·
発行者 Let's Encrypt / YR1· stored validity ends in 49 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
198.38.92.102
Network ASN
AS51713
Organization
WHG Hosting Services Ltd
Observed location
London, GB
Server header
LiteSpeed
ネームサーバー 1
ns2.uplserver3.com
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YR1
Valid from
2026-09-01 09:39:06
Valid until
2026-11-30 09:39:05
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-07 19:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint78c3bbe7e4a787be3332967d31e9131de3d3287a5433ea97df75b6048208d6b0Certificate names · 9 SANs
autodiscover.hsbccpersonalonlinebanking.com
cpanel.hsbccpersonalonlinebanking.com
cpcalendars.hsbccpersonalonlinebanking.com
cpcontacts.hsbccpersonalonlinebanking.com
hsbccpersonalonlinebanking.com
mail.hsbccpersonalonlinebanking.com
webdisk.hsbccpersonalonlinebanking.com
webmail.hsbccpersonalonlinebanking.com
www.hsbccpersonalonlinebanking.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Http 2xx Unclassified40%2026-10-11 10:08:10 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-10 10:07:23 UTClast content: 2026-10-10 10:07:23 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.
Last analyzed Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
カスペルスキー
SOCRadar
ソフォス
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Status Check2026-10-07 05:31:42 UTC
Telemetry event observed.
Threat First Observed2026-10-07 05:30:57 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 198.38.92.102.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
