VirusTotal
15 / 91 engine detections
Mở báo cáo“Parked Domain name on Hostinger DNS system”
Giả mạo Wordpress: midnightnetwork.online — Hoạt động được biết đến lần cuối (HTTP 200). Tóm tắt bằng chứng: VirusTotal 15/91 (ADMINUSLabs, ChainPatrol…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
15 / 91 engine detections
Mở báo cáo24 community references
Mở báo cáoprovider verdict: clean
Mở báo cáoNo threat flag
Mở báo cáoNo malicious flag
Mở báo cáoResults 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.
Có thể truy cập→Không có sẵn
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không có sẵn→Có thể truy cập
Có thể truy cập→Không có sẵn
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→live_content
content_served
Không rõ→inactive
expired_landing_page · lifecycle_notice_page
Không rõ→inactive
expired_landing_page · lifecycle_notice_page
Không rõ→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Được 1 thành viên cộng đồng báo cáo; ghi nhận lần đầu 14/12/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.