VirusTotal
6 / 91
“meets-on.online is registered at Namecheap”
The domain meets-on.online was registered on July 20, 2026 through Namecheap Inc. It resolves to the IPv4 address 192.64.119.9 and is served by the authoritative nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. The domain appears on a single public blocklist and is currently listed as blocked by the PhishDestroy feed, indicating that at least one anti-phishing community has observed malicious use. VirusTotal records show that the domain was submitted for analysis and scanned by 95 AV engines, none of which returned a positive detection at the time of scanning. While the lack of detections does not prove the site to be benign, it suggests that the payload may be novel or that the content has not yet triggered existing signatures. No information on SSL/TLS configuration, HTTP response codes, Safe Browsing status, OTX mentions, or page title has been published, so the surface-level behavior of the site remains uncharacterized. The rapid creation-to-activation timeline (one day between registration and first appearance on blocklists) is consistent with a “drop-and-run” phishing infrastructure that leverates freshly-registered domains to evade reputation-based controls. Defenders should consider adding the IPv4 address 192.64.119.9 to outbound and inbound deny lists, enforce DNS filtering for the domain, and monitor for any future detections associated with the registrar-servers nameservers. Continuous re-scanning with multi-engine services and inclusion in internal URL reputation feeds are recommended to capture any evolving malicious payloads. Until additional telemetry such as page content, SSL certificates, or HTTP headers becomes available, the domain should be treated as a high-confidence phishing indicator based on its blocklist presence and registrar profile.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
namecheap-nginxScanner note: redirect: raw=redirect_302; http=302; via=http_proxy; location=http://www.meets-on.online/; server=namecheap-nginx
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.comeforward1.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
10 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