VirusTotal
15 / 91 engine detections
Відкрити звіткрадіжка облікових даних: jonnienesimy.online — Контент недоступний. Зведення доказів: VirusTotal 15/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, CRDF…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
15 / 91 engine detections
Відкрити звітDBL_MALWARE
Scan report
Відкрити звіт7 community references
Відкрити звіт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
This domain, jonnienesimy.online, is flagged as a fake login portal designed to harvest user credentials. Analysis indicates the site mimics legitimate login pages to trick visitors into entering sensitive information such as usernames, passwords, or other authentication details. Once submitted, this data is typically transmitted to threat actors for unauthorized access, account takeovers, or further malicious activities like identity theft or financial fraud. The domain’s infrastructure and lack of legitimate use cases strongly suggest it operates solely for phishing purposes. Infrastructure analysis reveals multiple technical indicators confirming the malicious nature of this domain. It was registered on August 10, 2025, through NAMECHEAP INC, a registrar frequently associated with newly created phishing domains. The domain resolves to the IP address 5.182.38.147, hosted under AS209847 (WorkTitans B.V.), an autonomous system with a history of hosting suspicious activity. Security vendors have flagged the domain, with 19 out of 95 engines on VirusTotal detecting it as malicious. Additionally, it appears on one security blocklist, and no valid SSL certificate is present, further reducing its legitimacy. The domain’s current offline status suggests takedown efforts or evasion tactics by the operators. If you visited jonnienesimy.online or entered any credentials on the site, immediate action is required to mitigate risks. First, change the passwords for any accounts that may have been exposed, prioritizing email, financial, and work-related services. Enable multi-factor authentication (MFA) wherever possible to add an extra layer of security. Monitor your accounts for unusual activity, such as unauthorized logins or transactions, and report any suspicious findings to the relevant service providers. If financial information was entered, contact your bank or payment provider to flag potential fraud. Finally, scan your device for malware using updated security tools to ensure no additional compromise has occurred. Users should also report the domain to their organization’s security team or relevant authorities to aid in broader threat mitigation efforts.
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.
dns1.registrar-servers.comdns2.registrar-servers.comLocation describes the IP network.
273b6013005117d64a22596870758200b99c2966cf5494757a9a3392d498776aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
15/91 engine detections
View sourcePage captured
View sourcePD-20260622-AA884E
7 community references
View sourceNo threat flag
View sourcejonnienesimy.online
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
jonnienesimy.online
PD-20260622-AA884E Recipient: abuse@abusetracker.net Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
jonnienesimy.online)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.