ht.jpxzf.site
ht.jpxzf.site — Доступен · доступ ограничен (HTTP 403). Олицетворение бренда: Unknown. Сводка доказательств: VirusTotal 3/89 (alphaMountain.ai, Gridinsoft, LevelBlue); URLQuery 3 alerts; URLScan capture; PhishDestroy score 71/100. Регистратор: GoDaddy.
Подробный анализ PhishDestroy AI ниже оставлен на английском, чтобы сохранить исходную криминалистическую запись.
Сводка доказательств
ht.jpxzf.site is a subdomain of jpxzf.site. PhishDestroy first observed the hostname on Sep 20, 2026. Stored content metadata identifies Unknown as the apparent target. Current evidence score: 71/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and URLQuery. VirusTotal recorded 3 detections among 89 engines: alphaMountain.ai, Gridinsoft, LevelBlue on Sep 20, 2026 at 12:26 UTC. URLQuery recorded 3 threat-system alerts on Sep 20, 2026 at 04:17 UTC. Non-positive and contextual checks: ScamAdviser assigned a trust score of 15/100 (Very Likely Unsafe); no observation timestamp was retained. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 10:20 UTC. Google Safe Browsing returned no flag on Sep 20, 2026 at 12:26 UTC. URLScan captured the page on Sep 20, 2026 at 04:16 UTC.
An access-restricted HTTP 403 response was recorded on Sep 20, 2026 at 11:04 UTC. Registration records for the registrable domain jpxzf.site list GoDaddy.com, LLC as the registrar and Aug 17, 2026 as the creation date. At collection time, the hostname resolved to 172.67.145.165 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Sep 20, 2026 at 06:20 UTC returned 71/100. The evidence archive retains 4 visual captures from PhishDestroy, URLScan, and URLQuery; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Google Trust Services / WE1 as the certificate issuer with validity through Nov 15, 2026; checked Sep 20, 2026 at 07:02 UTC.
The content indicators and 2 positive source findings support the current Unknown impersonation and phishing classification. The target field identifies Unknown, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.
Данные сетевой безопасности
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | oss.carrefour-gl.vip |
malicious | Sinkholed |
| Quad9 DNS | oss.carrefour-gl.vip |
malicious | Sinkholed |
| Cloudflare DNS | oss.carrefour-gl.vip |
malicious | Sinkholed |
Forensic History & Detection Timeline
-
Domain Status Transition Sep 20, 2026 · 13:04 UTCDomain state transitioned from alive to dead.
-
VirusTotal Detections Update Sep 20, 2026 · 12:23 UTCVirusTotal scanner detections updated from 2 to 3. Added scanner alerts: alphaMountain.ai.
-
Threat First Observed Sep 20, 2026 · 06:13 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
172.67.145.165.
Процесс реагирования на угрозы
Статус в публичных блок-листах
Evasion analysis
Cloaking & traffic-distribution check
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
cloudflare
Scanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_direct; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
Сохранённый снимок · 4 sources
Аналитика доменов
Технические деталиDNS, SAN в протоколе SSL, временные метки
ICANN OVERSIGHT
Registration: jpxzf.site
Аккредитация и контекст RAA
Аккредитация и контекст RAA
Registrar accreditation and DNS abuse obligations
For the registrable domain jpxzf.site behind this subdomain, 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.
Технологии · 4 identified
Анализ VirusTotal
Анализ производительности сайта
Google PageSpeed Insights — mobile performance audit of ht.jpxzf.site · checked Sep 20, 2026
Доказательства и внешние отчеты
PD-20260920-C24DC1 Recipient: abuse@godaddy.com Abuse notice text as sent to the provider
Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Повлиял ли на вас этот сайт?
Если вы ввели учетные данные, личную или платежную информацию или загрузили файл с этого домена, примите немедленные меры. Ниже приведены ресурсы, которые помогут вам сообщить об инциденте и защитить себя.
Сообщите об этом в местные органы власти
Выберите свою страну, чтобы получить официальные контакты по киберпреступности или создать проект жалобы →.
Проверить любой домен
Анализ угроз с использованием сохраненного черного списка, WHOIS, DNS и общедоступных доказательств сканирования.
Сканировать сейчасСообщить о фишинге
Добавляйте подозрительные домены в нашу базу данных угроз — защищайте сообщество
СообщитьПоток оперативных данных об угрозах
Недавние сообщения о фишинге и наблюдаемые изменения доступности
ОтслеживатьБудьте в курсе событий, берегите себя
Отслеживайте актуальные угрозы или оспорьте эту запись, если считаете, что это ложное срабатывание