certs.armt.cloud returned HTTP status 301 on 2026-10-01, according to the recorded HTTP check. The same evidence set records a first observation of the domain on 2026-09-27, and a PageSpeed performance score of 55 on that date.
Recorded Evidence
PhishFeed listed certs.armt.cloud on the external blocklist checked 2026-10-01, and the domain also appears in the PhishDestroy internal listing. VirusTotal recorded 12 detections across 91 scanners on 2026-10-01. The recorded IP address is 35.190.118.211, located in the US.
Interpretation
The PhishFeed listing and the PhishDestroy internal listing are separate source records, each reflecting that source's own observation of certs.armt.cloud. The VirusTotal detection count and scanner total describe only that platform's recorded scan result. The HTTP 301 response describes the recorded response on its check date, not all content served by the domain.
Recommended Actions
Preserve the PhishFeed listing, the PhishDestroy internal listing, and the VirusTotal scan record for certs.armt.cloud as separate source artifacts. Compare the PhishFeed and PhishDestroy records against each other to see whether they describe the same observation. Recheck the HTTP response and the VirusTotal scan result for certs.armt.cloud at a later date, and compare each new result with its own earlier record.
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-13 22:08:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:25 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
ESET
Emsisoft
Fortinet
Gridinsoft
卡巴斯基
Lionic
Netcraft
SOCRadar
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of certs.armt.cloud· checked Sep 27, 2026
55
Needs Work
Performance
FCP
14.52s
First Contentful Paint
LCP
15.31s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
101ms
Total Blocking Time
SI
14.52s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-28 19:04:44 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-28 13:52:56 UTC
VirusTotal scanner detections updated from 11 to 4. Resolved alerts: CRDF, ESET, Gridinsoft, Kaspersky, OpenPhish, SOCRadar, alphaMountain.ai.
Threat First Observed2026-09-27 03:24:06 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 35.190.118.211.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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)
