Stored evidence for log-linkedin.com: VirusTotal recorded 8 detections among 89 scanners on 2026-09-17. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish and Phishunt appear as named external blocklist observations for log-linkedin.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 8 detections among 89 scanners in the stored snapshot dated 2026-09-17. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-17 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish and Phishunt are recorded as named external blocklist observations for log-linkedin.com in the snapshot dated 2026-09-17. The stored OpenPhish and Phishunt blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains log-linkedin.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish and Phishunt external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed log-linkedin.com on 2026-09-17. The OpenPhish and Phishunt blocklist snapshot is dated 2026-09-17 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-16. A URLScan reference was stored on 2026-09-17 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For log-linkedin.com, the registrar field records Key-Systems GmbH; this is kept as an exact source value. The source stores 92.118.126.145 as the observed address in this record. The registration date for log-linkedin.com is recorded as 2026-09-16. The stored ASN observation records 62005 and BlueVPS OU in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The log-linkedin.com record states that VirusTotal recorded 8 detections among 89 scanners on 2026-09-17. OpenPhish and Phishunt remain named blocklist observations from the snapshot dated 2026-09-17. PhishDestroy remains a separate publisher catalogue entry in the stored record. For log-linkedin.com, the registrar field records Key-Systems GmbH; this remains separate from the other source fields. The observed address field in this record contains 92.118.126.145. The supported conclusion is bounded to the exact stored observations for log-linkedin.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to log-linkedin.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain log-linkedin.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish and Phishunt blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to log-linkedin.com. The stored record does not justify extending that rule to 92.118.126.145 or to other infrastructure records.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='log-linkedin.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
DOM Analysisanalyzed 2026年9月17日score 98/1002 brand signals
IoC Extractionscanned 2026年9月18日1 wallet · 0 Telegram IoC
Submitted URLhttp://log-linkedin.com/
Favicon Hash
ケース ID
ページタイトル
LinkedIn: Log In or Sign Up
Impersonates
LinkedInMicrosoft
TLS証明書
Hostname coverage not recorded·
発行者 YR1
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
92.118.126.145
Network ASN
AS62005
Organization
BV Na39
Observed location
Los Angeles, US
Server header
nginx/1.30.5
ネームサーバー 6
dns1.monsterdns.net
dns2.monsterdns.net
dns3.monsterdns.net
ns1.rrpproxy.net
ns2.rrpproxy.net
ns3.rrpproxy.net
Location describes the IP network.
TLS証明書
Issuer
YR1
Hostname coverage
Hostname coverage not recorded
Collection time
2026-09-18 01:02:16 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:29:49 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-17 13:33:45 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-17 13:33:45 UTC → 2026-09-30 16:14:55 UTC · 314.69hmidpoint estimate ≈ 2026-09-24 02:54:20 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.
使用技術 · 2 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Last analyzed Previous stored snapshot: 8 detections
alphaMountain.ai
CRDF
Emsisoft
Fortinet
カスペルスキー
ネットクラフト
OpenPhish
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of log-linkedin.com· checked Sep 17, 2026
55
Needs Work
Performance
FCP
2.41s
First Contentful Paint
LCP
5.91s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
549ms
Total Blocking Time
SI
7.11s
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.
Domain Status Transition2026-09-19 22:48:16 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-17 13:32:33 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 92.118.126.145.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 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)
