certs.armt.cloud is an impersonation phishing page that presents itself as ARMT Cloud. Its page title reads simply "ARMT Cloud", and it targets people who expect a genuine ARMT Cloud service. PhishDestroy first flagged it on 2026-09-27. As of 2026-10-19 the site was still online and its content was reachable through a redirect.
How the scam works
Impersonation pages like this copy a brand's name and look so the visitor believes they have reached the real service. The "certs" subdomain suggests a certificate or account-management area, which makes a login or verification prompt seem routine. Whatever is typed into such a page, including usernames, passwords and one-time codes, goes to the operators. They can then take over the account and anything reachable through it. The redirect means the first address a visitor lands on may forward them to the page that actually collects their details.
Evidence
On 2026-10-01, 12 of 91 VirusTotal engines flagged the domain. The vendors include alphaMountain.ai, CRDF, ESET, Emsisoft, Fortinet, Gridinsoft, Kaspersky and Lionic. Several major endpoint-security products are among them, so many users running that software will already be warned or blocked. Most engines had not yet caught up, however, and a clean result from one scanner should not be read as a sign of safety. PhishDestroy lists the domain on its own blocklist.
Infrastructure
The parent domain armt.cloud was registered on 2021-01-12 through NAMECHEAP INC, more than five years before PhishDestroy detected this subdomain. An aged domain does not trip the "newly registered" filters many security tools rely on. The site is hosted on Google Cloud Platform in the US and uses a Google Trust Services certificate. A valid padlock therefore says nothing about whether the page is legitimate.
What to do
If you entered credentials on this page, change the ARMT Cloud password right away, along with any other account that shares it. Then turn on or reset two-factor authentication and sign out of all active sessions. Review recent account activity, API keys and connected applications for anything you did not set up. Reach ARMT Cloud only by typing its known address or using a saved bookmark, never through links in emails or messages. Defenders should block certs.armt.cloud at DNS and web proxies and search logs for users who visited it. Anyone whose credentials may have been exposed should have them reset.
Registration (base domain)armt.cloud · 생성됨 2021년 1월 12일 —Expires 2027년 1월 12일
HTTP 상태301 Moved Permanently
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 27일
DOM Analysisanalyzed 2026년 10월 9일score 88/100
Submitted URLhttp://certs.armt.cloud/
Favicon Hash
ICANN OVERSIGHTRegistration: armt.cloud
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For the registrable domain armt.cloud behind this subdomain, 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 fingerprint4280c9362754bc0b1ef15ff2a6a371c4fd0bc8560ea214d46fa33ddb985f04a8Certificate names · 2 SANs
armt.cloud
terminal.armt.cloud
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:27:43 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-19 22:35:30 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.
기술 · 7 identified
R
Ruby
Programming languages
Ruby is an open-source object-oriented programming language.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
지금 당장 어떻게 해야 할까요?
긴급
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 certs.armt.cloud)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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.
(US)
