Analysis of the domain www.kreditbk.io, created on August 12, 2025, shows a clear infrastructure pattern associated with brand impersonation campaigns. The domain resolves to the IPv4 address 82.29.189.219, which is assigned to AS47583 Hostinger International Limited and geolocated to the United Kingdom. The authoritative name servers are ns1.dns-parking.com and ns2.dns-parking.com, typical of domains parked on generic DNS services. No SSL/TLS certificate is presented, indicating that the site was served over plain HTTP when it was reachable.
The page title returned by the server reads “Kredit bank - Dedicated to innovating, simplifying, and humanizing digital banking,” suggesting an attempt to mimic a legitimate banking brand, although the exact target brand is not confirmed beyond the generic “across” label in the intelligence feed. Registration details list HOSTINGER operations, UAB as the registrar, aligning with the hosting ASN. VirusTotal reports a single positive detection out of 95 scanning engines, and the domain appears on one public blocklist, corroborated by a block entry from PhishDestroy. Gridinsoft assigns a trust score of 0 / 100, reinforcing the malicious classification.
The domain is currently offline, which may be the result of takedown actions or automated sink‑holeing. Uncertainty remains regarding the full scope of the campaign, such as the specific victim list, the presence of credential‑harvesting pages, or any additional infrastructure components that may have been deployed elsewhere. Defenders should update URL filtering and DNS block policies to include www.kreditbk.io, monitor Hostinger‑hosted IP ranges for similar patterns, and advise users to avoid entering credentials on any site lacking a valid TLS certificate that claims to represent a banking institution. Continuous observation of the host ASN and associated parking name servers is recommended to detect future re‑registrations that may reuse the same infrastructure.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-7580.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
DOM Analysisanalyzed 2026年4月23日score 56/1003 brand signals
Submitted URLhttps://www.kreditbk.io/
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:12:21 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-14 22:17:45 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.
11 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.
(LT)
