On 2026-10-01, standrem.de returned an HTTP status 200, confirming a successful response at that time. The domain also achieved a PageSpeed performance score of 99 on 2026-09-27, indicating a high level of measured efficiency.
Recorded Evidence
The HTTP status for standrem.de was recorded as 200 on 2026-10-01. VirusTotal reported 16 detections out of 91 scanners on 2026-09-29. The domain was first observed on 2026-09-27, and its PageSpeed performance score was 99 on that date. OTX noted 4 pulses on 2026-09-29, and the domain is listed in the internal PhishDestroy catalogue.
Interpretation
These observations provide a snapshot of standrem.de's recorded activity and performance from several sources. The HTTP response and PageSpeed score reflect technical measurements, while VirusTotal, OTX, and the PhishDestroy listing document external assessments. The dates allow comparison of the domain's status as observed by each source.
Recommended Actions
For standrem.de, preserve the HTTP status record and PageSpeed score for technical reference. Retain the VirusTotal, OTX, and PhishDestroy records for ongoing review and comparison. Avoid submitting sensitive information to the domain until its evidence can be further evaluated.
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: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:09:53 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:09:53 UTClast content: 2026-10-11 10:09:53 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.
脅威情報の照合 · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
Last analyzed Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
カスペルスキー
LevelBlue
Lionic
MalwareURL
ネットクラフト
SOCRadar
ソフォス
URLQuery
VIPRE
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of standrem.de· checked Sep 27, 2026
99
Good
Performance
FCP
0.85s
First Contentful Paint
LCP
1.54s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.32s
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 23:13:20 UTC
VirusTotal Detections Update2026-09-27 12:15:27 UTC
VirusTotal scanner detections updated from 8 to 9. Added scanner alerts: MalwareURL.
VirusTotal Detections Update2026-09-27 08:06:06 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-27 06:33:53 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: Gridinsoft.
Threat First Observed2026-09-27 03:23:05 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 31.76.120.174.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
