VirusTotal
8 / 91
“Vote”
The sent-report ledger records the first outgoing report at .
The recorded recipient is report@abuseradar.com.
The latest stored availability evidence still shows the domain reachable; 12 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.
helplisting.forum — Неперевірений. Уособлення бренду: ["coinmarketcap"]; Тип шахрайства: Impersonation. Зведення доказів: VirusTotal 8/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft); URLQuery 2 det.; Spamhaus DBL_SPAM; 1 external blocklist match (ScamSniffer); PhishDestroy score 100/100. Реєстратор: Registrar.eu.
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
8 / 91
2 det.
ПовідомитиDBL_SPAM
4 community references
Повідомитиprovider verdict: suspicious
Повідомитизбережений звіт
Повідомити Аналіз завершено
ПовідомитиChecked; no threat flag recorded
ПовідомитиStored evidence for helplisting.forum: VirusTotal recorded 2 detections among 91 scanners on 2026-09-29. That ratio reproduces the stored check in its original units and is not converted into another measure. ScamSniffer appear as named external blocklist observations for helplisting.forum. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 2 detections among 91 scanners in the stored snapshot dated 2026-09-29. 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-29 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.
ScamSniffer are recorded as named external blocklist observations for helplisting.forum in the snapshot dated 2026-09-29. The stored ScamSniffer blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains helplisting.forum as a publisher record. That PhishDestroy record is counted separately from the ScamSniffer 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 helplisting.forum on 2026-09-29. The ScamSniffer blocklist snapshot is dated 2026-09-29 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-21. A URLScan reference was stored on 2026-09-29 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 96.62.224.122 as the observed address in this record. The registration date for helplisting.forum is recorded as 2026-09-21. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-09-29. The stored ASN observation records 207043 and DEDIK SERVICES LIMITED in this record. 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 helplisting.forum record states that VirusTotal recorded 2 detections among 91 scanners on 2026-09-29. ScamSniffer remain named blocklist observations from the snapshot dated 2026-09-29. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 96.62.224.122. The supported conclusion is bounded to the exact stored observations for helplisting.forum. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to helplisting.forum during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain helplisting.forum as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and ScamSniffer 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 helplisting.forum. The stored record does not justify extending that rule to 96.62.224.122 or to other infrastructure records.
Збережені дані спостережень за взаємодією веб-сканера та браузера для цього хоста, а також перевірка відбитків у режимі реального часу для систем розподілу трафіку типу «Кейтаро».
Примітка щодо сканера: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='helplisting.forum', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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.
addyson.ns.cloudflare.comchuck.ns.cloudflare.comLocation describes the IP network.
b5f5c7060aaf95f6e59ecb4a93cde47e9428c676408536f361e8d8a12dae0814Saved 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 helplisting.forum · checked Sep 29, 2026
96.62.224.122. 13 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-20260929-2A7C2B Recipient: report@abuseradar.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 і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога