ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@aquiryn.com.
The latest stored availability evidence still shows the domain reachable; 29 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
ft-bkfinance.com returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-12, and its registration date is listed as 2025-12-08 with NameSilo, LLC as registrar.
Recorded Evidence
The recorded HTTP check on 2026-10-01 produced status 200, while the first observation of ft-bkfinance.com dates to 2026-09-12. A PageSpeed check on 2026-09-12 returned a performance score of 91. VirusTotal recorded 15 detections across 89 scanners on 2026-09-20. The SSL scan on 2026-09-13 identified YR2 as the certificate issuer. The domain appears in the PhishDestroy internal listing, and the IP address 23.153.104.17 is associated with AS32561 Aquiryn LLC in the US.
Interpretation
The VirusTotal count from 2026-09-20 and the PhishDestroy internal listing reflect observations made on different dates, so their relationship cannot be treated as simultaneous. The HTTP check on 2026-10-01 and the SSL scan on 2026-09-13 likewise come from separate points in time, meaning the records describe distinct snapshots rather than one continuous state. Because the observation dates differ, comparisons between these sources should account for the gap between each measurement.
Recommended Actions
Anyone reviewing ft-bkfinance.com should retain the dated records, including the HTTP check, PageSpeed result, SSL scan, VirusTotal count and PhishDestroy listing, so later observations can be compared against them. Subsequent checks of ft-bkfinance.com should be logged with their own dates and values to show how the recorded data changes over time. During review, avoid submitting sensitive information to the domain until the available records have been fully assessed.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-11 10:24:33 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:24:33 UTClast content: 2026-10-09 10:26:22 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.
Google PageSpeed Insights — mobile performance audit of ft-bkfinance.com· checked Sep 12, 2026
91
Good
Performance
FCP
2.45s
First Contentful Paint
LCP
2.6s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.52s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-09-12 11:56:08 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.153.104.17.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
12 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(US)
PhishDestroy Investigation
