dodsman.com was first observed on 2026-10-11, and an OTX record from 2026-10-12 documents its presence in 38 OTX pulses. The domain is also included in an internal PhishDestroy listing.
Recorded Evidence
VirusTotal checked dodsman.com on 2026-10-11, recording 13 detections out of 92 scanners. OTX reviewed the domain on 2026-10-12 and found it referenced in 38 pulses. The domain's registration date is recorded as 2025-10-30 by Dynadot Inc. PhishDestroy has an internal listing for dodsman.com as of the current evidence.
Interpretation
The VirusTotal record contains a technical measurement of detections across multiple scanners, providing a snapshot of how the domain was assessed by security vendors. OTX records the domain's presence in several intelligence pulses, which can reflect its mention in threat research or monitoring feeds. The inclusion in the PhishDestroy internal listing documents that dodsman.com is catalogued for further review within that system. These sources together cover detection, intelligence, and internal tracking from late 2025 through 2026.
Recommended Actions
To track dodsman.com, retain the VirusTotal and OTX records for future comparison with updated security scans and intelligence feeds. Review the PhishDestroy internal listing for any changes or added context in subsequent assessments. Use these dated records as reference points for monitoring changes in detection and intelligence coverage.
Hostname coverage not recorded·
颁发者 ZeroSSL RSA DV SSL CA 2
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
34.41.139.193
Network ASN
AS396982
Organization
Google Cloud (us-central1)
Observed location
Council Bluffs, US
Server header
nginx
域名服务器 1
ns2.hwrn.net
Mail routing 2 MX records
mx1.csof.netpriority 10
mx2.csof.netpriority 10
Location describes the IP network.
TLS 证书
Issuer
ZeroSSL RSA DV SSL CA 2
Hostname coverage
Hostname coverage not recorded
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.
Latest HTTP observation未知Empty Response20%2026-10-13 01:35:46 UTC
RDAP registration未知
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.
技术 · 1 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.
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 11:19:22 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.41.139.193.
威胁响应 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)
