VirusTotal
7 / 91
“HPH | HIGH TECH SEGELFLUGZEUGE”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ascio.com.
The latest stored availability evidence still shows the domain reachable; 25 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
304shark.info — Останній відомий активний (HTTP 200). Тип шахрайства: Impersonation. Зведення доказів: VirusTotal 7/91 (Criminal IP, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft); URLQuery 2 alerts; Spamhaus DBL_ABUSED_PHISH; PhishDestroy score 90/100. Реєстратор: Ascio Technologies.
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
7 / 91
2 threat-system alerts
ПовідомитиDBL_ABUSED_PHISH
4 community references
Повідомитиprovider verdict: clean
Повідомитизбережений звіт
Повідомити Аналіз завершено
Повідомити80/100
ПовідомитиChecked; no threat flag recorded
ПовідомитиStored evidence for 304shark.info: VirusTotal recorded 3 detections among 89 scanners on 2026-09-17. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for 304shark.info. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 3 detections among 89 scanners in the stored snapshot dated 2026-09-17. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-17 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
OpenPhish are recorded as named external blocklist observations for 304shark.info in the snapshot dated 2026-09-17. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains 304shark.info as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed 304shark.info on 2026-09-17. The OpenPhish blocklist snapshot is dated 2026-09-17 and remains a separate event in the stored timeline. The registration date is separately recorded as 2014-11-07. A URLScan reference was stored on 2026-09-17 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
The source stores 194.30.191.151 as the observed address in this record. The registration date for 304shark.info is recorded as 2014-11-07. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-09-17. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The 304shark.info record states that VirusTotal recorded 3 detections among 89 scanners on 2026-09-17. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-17. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 194.30.191.151. The supported conclusion is bounded to the exact stored observations for 304shark.info. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to 304shark.info during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain 304shark.info as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to 304shark.info. The stored record does not justify extending that rule to 194.30.191.151 or to other infrastructure records.
Збережені дані спостережень за взаємодією веб-сканера та браузера для цього хоста, а також перевірка відбитків у режимі реального часу для систем розподілу трафіку типу «Кейтаро».
BitNinja-WafProПримітка щодо сканера: alive_content: raw=ok; http=200; via=https_direct; server=BitNinja-WafPro
Репутація Edge-IP не пов’язана з цим доменом.
ns5.pwrz.atns6.pwrz.atmailgate5.pwrz.atpriority 10mailgate6.pwrz.atpriority 10Location describes the IP network.
17ba23def38e206e1753c8952db2b52bcb4403d85073fb0b35330824d090b1a4Saved 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 304shark.info · checked Sep 17, 2026
194.30.191.151. 11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
PD-20260917-E6F072 Recipient: abuse@ascio.com 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.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога