The domain microsoftupdater.info was listed in the CryptoFirewall blocklist on 2026-10-13, providing a dated record of its inclusion in an external security listing. VirusTotal also recorded detections for this domain, offering a quantitative perspective from a separate source.
Recorded Evidence
CryptoFirewall included microsoftupdater.info in its external blocklist on 2026-10-13. VirusTotal checked the domain on 2026-10-11, documenting 21 detections out of 92 total scanners. OTX referenced this domain in four pulses as of 2026-10-13. The registrar is Turkticaret.net Yazılım Hizmetleri Sanayi ve Ticaret A.Ş., with a registration date of 2026-06-16. PhishDestroy internally listed the domain according to the latest available evidence.
Interpretation
VirusTotal provides a measurement of how many security scanners detected microsoftupdater.info, reflecting its status across multiple scanning engines. OTX records show that the domain has been referenced in several community-sourced intelligence entries. The CryptoFirewall blocklist documents its inclusion in an external listing, adding another perspective to the domain's security profile.
Recommended Actions
Preserve the CryptoFirewall blocklist entry and VirusTotal detection record for microsoftupdater.info for future reference and comparison. Retain the OTX pulse references and the PhishDestroy internal listing as part of the domain's evidence profile. Regularly review these source records to monitor for any new developments or changes related to this domain.
IP 信誉abuse score 0/1000 reportschecked 2026年10月13日
OTX Tags107-170-109-82-808032-bitagentteslaamosamos helperanimateclipperarmasciiblocklistbotnetbotnetdomainbroadwalkindiac2-monitor-autoclearfake+6 more
Certificate hostname mismatch·
颁发者 Let's Encrypt / YR1· stored validity ends in 74 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
104.239.83.200
Network ASN
AS215391
Organization
CAFER ESER
Observed location
Istanbul, TR
Server header
nginx
域名服务器 1
ns3.turkticaret.net
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt / YR1
Valid from
2026-09-28 22:43:47
Valid until
2026-12-27 22:43:46
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-13 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7f1df6c32b053ed7c2f9126b13b1bb3d3813c4545debca8bdb1276eba9aae4aeCertificate names · 1 SANs
feserver.betterwith.agency
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:00:16 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:00:16 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.
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.
Threat First Observed2026-10-12 23:34:26 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.239.83.200.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 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.
