http://palcay.de/sappshttp://palcay.de/HTTP 404
0 B
20 B
0 internal · 0 external
Server: nginxContent-Type: text/plainAll stored response-header names (5)
ServerDateContent-TypeTransfer-EncodingConnectionThe sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 10 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
“Site is created successfully!”
The domain palcay.de is currently listed on a public security blocklist and remains active as of the report date, July 30, 2026. DNS resolution points to the IPv4 address 9.205.104.141, which is served by the authoritative nameservers atlas.dns-parking.com and hyperion.dns-parking.com – both commonly associated with parked or monetized domains. The presence of these parking nameservers suggests that the domain is not hosted on a dedicated web server but is instead leveraging a shared infrastructure that can be rapidly repurposed for malicious campaigns. The domain has been flagged by the PhishDestroy blocklist, confirming that at least one anti‑phishing feed has identified it as a threat.
VirusTotal analysis shows that three out of ninety‑one scanning engines have generated a detection, indicating that a minority of security products have recognized malicious activity associated with the domain, while the majority have not yet flagged it. This mixed detection profile underscores the need for defenders to treat the domain as suspicious even in the absence of a consensus across all vendors. No additional intelligence such as page titles, SSL certificate details, or specific brand impersonation has been disclosed, leaving the exact phishing lure undefined.
Consequently, security teams should block outbound connections to 9.205.104.141 and prevent DNS resolution of palcay.de at network perimeters. Continuous monitoring of threat‑intel feeds for any escalation in detection counts or additional blocklist listings is advised, as further analysis may reveal the targeted brand or payload characteristics. Until more granular evidence emerges, the domain should be considered a high‑risk phishing indicator and handled accordingly.
已发送报告记录
PD-20260730-CE09EB| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | palcay.de |
malicious | Sinkholed |
10 个来源 · 于 2026年8月10日 同步
按时间顺序显示已存储的观测记录。
已存储的观测记录:首次观测为 alive
已存储的观测记录:alive → dead
已存储的观测记录:dead → alive
识别出 3 项高置信度技术
Google PageSpeed Insights — mobile performance audit of palcay.de · checked Jul 30, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://palcay.de/sappshttp://palcay.de/Server: nginxContent-Type: text/plainServerDateContent-TypeTransfer-EncodingConnection如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析
立即扫描将可疑域名提交至我们的威胁数据库——保护社区
报告最近的网络钓鱼报告和观察到的可用性变化
监控