amlget.vercel.app returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check for that date. The same record set notes a first observation of this domain on 2026-09-05, giving a bounded window for the earliest logged sighting.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 200 for amlget.vercel.app. A blocklist check dated 2026-10-01 counted one external listing, attributed to ScamSniffer. An SSL scan dated 2026-09-12 named Google Trust Services / WR1 as the issuer. A VirusTotal check dated 2026-09-14 reported 12 detections across 89 scanners. The domain also appears on the PhishDestroy internal listing.
Interpretation
These sources were collected on different dates, so the ScamSniffer listing, the SSL scan and the VirusTotal result describe separate moments rather than one synchronized view. Because the observation dates differ, a reader can compare what each source recorded at its own time without treating any single record as current. The named sources document observations; they do not by themselves describe content or intent.
Recommended Actions
Anyone reviewing amlget.vercel.app should retain the dated records exactly as captured, including the HTTP check, the ScamSniffer listing and the VirusTotal result, so later observations can be compared against them. A follow-up check of amlget.vercel.app should be logged with its own date and kept alongside the earlier entries rather than merged with them. During any review, avoid submitting credentials, payment details or other sensitive information to the domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:14:21 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:14:21 UTClast content: 2026-10-11 10:14:21 UTC
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.
使用技術 · 3 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
ネットクラフト
ソフォス
Webroot
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
脅威の検知
amlget.vercel.app 検出され、詳細な分析のためにキューに入れられた
2026年9月5日
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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)
