VirusTotal
5 / 91
“Calendly”
As of July 23, 2026, quickmeetup.online is under investigation for generic phishing activity. The domain remains active and has been operational since its creation on July 22, 2026. It is registered through NAMECHEAP INC and utilizes nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. The domain resolves to IP address 192.64.119.114. Notably, quickmeetup.online is currently blocked by PhishDestroy and is listed on one security blocklist, which signals that at least one external threat intelligence source has flagged it for potential abuse.
VirusTotal reports that 91 vendors have scanned the domain, and while none currently detect it as malicious, the absence of detections is not evidence of safety. Security analysts should treat this as an early-stage phishing threat, especially given the rapid activation and blocklist placement shortly after registration. The site’s detected infrastructure includes technologies such as Apple iCloud Mail, Ruby, Ruby on Rails, Stripe, Amazon Web Services, Salesforce Marketing Cloud Account Engagement, HubSpot, and HSTS. The presence of payment and marketing technologies can be leveraged in social engineering schemes, though no direct evidence of their malicious configuration is available at this time.
The exact website content and targeted brands or users are not yet analyzed. Given the active status, recent creation date, and blocklist evidence, defenders should monitor for emerging indicators of compromise and consider restricting access pending further review. Continued observation is recommended, with special attention to updates from security blocklists and detection platforms.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='quickmeetup.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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.
Edge-IP reputation is not attributed to this domain.
dns1.registrar-servers.comdns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive