VirusTotal
15 / 91 engine detections
レポートを開く“Parked Domain name on Hostinger DNS system”
Wordpressなりすまし: midnightnetwork.online — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 15/91 (ADMINUSLabs, ChainPatrol, alphaMountain.ai, BitDefender, Chong…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開く24 community references
レポートを開くprovider verdict: clean
レポートを開く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 midnightnetwork.online was registered on 24 September 2025 through HOSTINGER operations, UAB and is delegated to the authoritative name servers ns1.dns-parking.com and ns2.dns-parking.com. DNS resolution points to the single IPv4 address 84.32.84.32, which belongs to AS47583 Hostinger International Limited located in Lithuania. An HTTPS negotiation presents a certificate issued by Google Trust Services under the WR1 profile, indicating a valid TLS chain but offering no evidence of malicious signing. An HTTP GET returns status code 200 and the page title “Parked Domain name on Hostinger DNS system”, consistent with a parking page rather than a crafted phishing landing page.
The site employs Hostinger’s CDN, Google Analytics, and HTTP/3, all of which are typical of benign hosting services. VirusTotal analysis shows 12 of 95 scanners flagging the domain, and the Gridinsoft trust score is 0 / 100, reflecting a high‑risk assessment. The domain appears on a single external blocklist and has been actively blocked by the PhishDestroy service. AlienVault OTX includes the domain in one threat‑intel pulse, and the overall classification is “Brand Impersonation” targeting the WordPress brand.
No additional payloads, redirects, or credential‑harvesting forms have been observed; the current offline status prevents further content collection. Given the combination of a low trust score, multiple vendor detections, and explicit branding of WordPress impersonation, security teams should treat midnightnetwork.online as a high‑confidence malicious indicator. Recommended mitigations include adding the domain and its resolved IP to DNS‑based deny lists, extending web‑proxy filtering rules to block any HTTP(S) request to the address, and monitoring for new Hostinger‑parking domains that reference the same brand target. Continued vigilance is advised, as the underlying hosting infrastructure can be reused for future impersonation campaigns.
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.
ns1.dns-parking.comns2.dns-parking.comLocation describes the IP network.
c301b61d38bfc7fa7bf39d4f03289c6ad9ce4a31c7997019eff846362434b5dewww.midnightnetwork.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.midnightnetwork.onlineDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of midnightnetwork.online · checked Mar 2, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=hcdn
midnightnetwork.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→inactive
expired_landing_page · lifecycle_notice_page
不明→inactive
expired_landing_page · lifecycle_notice_page
不明→inactive
expired_landing_page · lifecycle_notice_page
No threat flag
View source24 community references
View source15/91 engine detections
View sourcePage captured
View sourcemidnightnetwork.online
View sourceコミュニティの 1 人が報告・初回確認 2025年12月14日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
midnightnetwork.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.