VirusTotal
3 / 93 engine detections
Відкрити звіт“Encrypted — End-to-End Secure Node”
фальшива техпідтримка: abhodlblock.support — Контент недоступний. Зведення доказів: VirusTotal 3/93 (Gridinsoft, Seclookup, SOCRadar); 3 external blocklist…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
3 / 93 engine detections
Відкрити звітSuspicious
Відкрити звітno community references
Відкрити звіт15 перевірено — блокувань немає
No threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain abhodlblock.support was registered on February 21, 2026 through Hostinger Operations UAB and resolves to the IP address 46.202.158.17, which belongs to AS47583 Hostinger International Limited located in Germany. The hosting environment reports LiteSpeed web server software, Hostinger branding, and HTTP/3 support, indicating a modern content delivery configuration. The site presented the page title "Encrypted — End-to‑End Secure Node" and served a Let’s Encrypt R13 certificate, but no additional page content has been captured because the service was taken offline before a full content grab could be performed.
VirusTotal analysis shows that three of ninety‑three security vendors flagged the domain, and Gridinsoft assigned a trust score of zero out of one hundred, reflecting a high likelihood of malicious intent. Four independent blocklists—PhishDestroy, Polkadot, Enkrypt, and Codeesura—have listed the domain, and it appears on a total of four security blocklists. The technical profile, combined with the classification as a tech‑support scam, suggests the domain was used to impersonate legitimate support services in order to obtain credentials or payment from victims.
Current evidence does not reveal the exact phishing page structure, payload, or victim interaction flow, leaving the precise attack vector uncertain. Defenders should continue to enforce blocklist rules for abhodlblock.support, monitor the associated IP range for related activity, and consider sinkholing or null‑routing the IP address to prevent further exploitation. Ongoing surveillance of newly created Hostinger‑hosted domains with similar TLS certificates and server fingerprints is recommended to detect future campaigns that may employ the same infrastructure.
Last checked
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.
ns2.dns-parking.comLocation describes the IP network.
32e01a697042c9165427855e28481b8f43c4f4515f2abb7f2d841af3c005b3fewww.abhodlblock.supportSaved 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.abhodlblock.supportDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of abhodlblock.support · 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.
abhodlblock.support
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Phishing Abuse Report: abhodlblock[.]support
No threat flag
View source3/93 engine detections
View sourceabhodlblock.support
View sourcePage captured
View sourceПовідомив 1 учасник спільноти; уперше помічено 21.01.2026
PD-1774186268-abhodlblock.sup Recipient: abuse@hostinger.com Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
abhodlblock.support)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.