VirusTotal
1 / 91 engine detections
Відкрити звіт“Zoho Meeting”
домен у блоклистах: secureconnect-zohomeet.online — Контент недоступний. Зведення доказів: VirusTotal 1/91 (Gridinsoft); 2 external blocklist matches…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
1 / 91 engine detections
Відкрити звітchecked — no detections recorded
Відкрити звітno community references
Відкрити звітprovider verdict: clean
Відкрити звіт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, secureconnect-zohomeet.online, is suspected of being a credential phishing site designed to steal login credentials from users. The threat posed by this domain is significant as it mimics the legitimate Zoho Meeting login page, potentially tricking users into entering their credentials on a fake site.
Analysis indicates that the domain was registered on June 25, 2026, through HOSTINGER operations, UAB. Despite its current active status, it has not yet been flagged by any of the 95 security engines on VirusTotal, which can suggest that it is a new or under-investigated threat. The domain resolves to the IP address 82.29.199.64 and uses an SSL certificate from Google Trust Services, which may lend a false sense of security to unsuspecting visitors.
If you have visited this site, it is crucial to take immediate action to protect your credentials. Change your Zoho Meeting login credentials and any other accounts where you may have used the same password. Monitor your account activity for any unauthorized access and report any suspicious incidents to the relevant service provider. Additionally, consider enabling two-factor authentication (2FA) for an added layer of security.
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.
apollo.dns-parking.comathena.dns-parking.comLocation describes the IP network.
9cdcd16d3afa0b8c1b6d0557829cb28bf215931c19d21147f94b955970861749www.secureconnect-zohomeet.onlineSaved 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.secureconnect-zohomeet.onlineDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of secureconnect-zohomeet.online · checked Jun 26, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='secureconnect-zohomeet.online', port=80): Max retries exceeded with url: / (Caused by NewC
secureconnect-zohomeet.online
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
1/91 engine detections
View sourcePage captured
View sourcePD-20260626-B449F4
No threat flag
View sourcesecureconnect-zohomeet.online
View sourcePD-20260626-B449F4 Recipient: report@abuseradar.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 ↗
secureconnect-zohomeet.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.