SSL certificate is invalid or expired. Issuer: Let's Encrypt / R13
证据摘要
关键
VirusTotal
11/91
OTX
16 community refs
URLScan
Stored capture
The domain meetappbot.online was registered on May 08, 2026 through NameCheap, Inc. and is hosted on a Hetzner Online GmbH server in Finland (IP 95.217.98.125). The authoritative nameservers are dns1.registrar-servers.com and dns2.registrar-servers.com. The site serves HTTP 200 responses and presents the page title "TG Meet" under a valid Let's Encrypt (R13) certificate. Infrastructure analysis shows a Gridinsoft trust score of 0/100, indicating a highly untrusted host. The domain appears on three public blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL. AlienVault OTX lists the domain in one threat‑intelligence pulse, and three independent security blocklists have flagged it. VirusTotal scanned the site with 92 vendors and reported no detections, but the lack of detections does not constitute evidence of safety. Current intelligence does not reveal the specific payload or credential‑harvesting mechanisms employed, and the page content has not been publicly analyzed. Defenders should block the domain at the network perimeter, monitor DNS queries for the associated IP and nameservers, and treat any credentials entered on the site as compromised. Ongoing observation of the domain’s activity and rapid response to any emerging indicators are recommended.
DOM Analysisanalyzed 2026年9月19日score 100/1001 brand signal
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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 fingerprint034086b630dd3a1af66497ab5eb4242792dd6bf320be35807d722e1975ed075fCertificate names · 1 SANs
www.meetappbot.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcome非活动reason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: ResolvedRegistration: Unknown
Latest HTTP observation非活动Http No Content70%2026-10-13 22:27:58 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-26 10:22:16 UTCcurrent episode first observed: 2026-10-01 02:34:12 UTCobserved RIP window: 2026-09-26 10:22:16 UTC → 2026-10-01 02:34:12 UTC · 112.20hmidpoint estimate ≈ 2026-09-28 18:28:14 UTC · precision 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.
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Sophos
VIPRE
威胁响应 Pipeline
发现
Analysis
Monitoring
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(US)
