VirusTotal
16 / 91 engine detections
レポートを開く“Kingdom Security Service”
認証情報フィッシング: kingdomsecurityservice.online — コンテンツが利用できません. 証拠の概要: VirusTotal 16/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 91 engine detections
レポートを開く2 det.
レポートを開く1 community reference
レポートを開くprovider verdict: clean
レポートを開く13 確認済み — ブロックなし
No threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain kingdomsecurityservice.online is currently active and hosted on an IP address (163.61.188.7) located in the United States. Registration data shows the domain was created on November 10, 2025 and is registered through Global Domain Group LLC. The authoritative nameservers are dns1.lytehosting.com, dns2.lytehosting.com, dns3.lytehosting.com, and dns4.lytehosting. The site presents a valid Let's Encrypt certificate (R12) and serves content over HTTP/3 with a LiteSpeed web server, jQuery, and returns HTTP 200 responses. Infrastructure analysis indicates the host is using LyteHosting services. Threat intelligence sources flag the domain as a credential phishing operation; it appears in one AlienVault OTX pulse and is listed on a single security blocklist. VirusTotal scans show 4 of 91 security vendors flag the domain, and PhishDestroy has already blocked it. Gridinsoft assigns a trust score of 0/100, reinforcing the malicious assessment. While the page title "Kingdom Security Service" is known, the exact credential‑collection mechanisms and targeted brands have not been publicly disclosed. Defenders should add the domain to outbound and inbound blocklists, monitor DNS queries for the associated IP and nameservers, and consider sinkholing the address to disrupt potential phishing campaigns. Continuous re‑evaluation is advised as additional threat intel may emerge.
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.
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.
dns1.lytehosting.comdns2.lytehosting.comdns3.lytehosting.comdns4.lytehosting.comns1.cprapid.comns2.cprapid.comLocation describes the IP network.
39c3c7e4f187bfa090c6a6ee577b63400a08b2b5d41c7f85ddf5cb127ab7b10bSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of kingdomsecurityservice.online · checked Jul 1, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='kingdomsecurityservice.online', port=80): Max retries exceeded with url: / (Caused by NewC
kingdomsecurityservice.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
4→4
16/91 engine detections
View source1 community references
View sourcePD-20260701-F47E31
No threat flag
View sourcekingdomsecurityservice.online
View sourcePage captured
View sourcePD-20260701-F47E31 Recipient: abuse@whiteprivacy.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
kingdomsecurityservice.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.