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.
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.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprint9cdcd16d3afa0b8c1b6d0557829cb28bf215931c19d21147f94b955970861749Certificate names · 1 SANs
www.secureconnect-zohomeet.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:09:37 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-07-03 16:18:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-03 16:18:07 UTC → 2026-09-30 16:14:55 UTC · 2,135.95hmidpoint estimate ≈ 2026-08-17 04:16:31 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1
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 record
The original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of secureconnect-zohomeet.online· checked Jun 26, 2026
98
Good
Performance
FCP
1.91s
First Contentful Paint
LCP
1.92s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.07s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
2135.95
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
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
保存済みの結果
到達不能
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
