ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@microsoft.com.
The latest stored availability evidence still shows the domain reachable; 24 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
On 2026-10-01, docuposte.secure-mailing-service.com returned an HTTP status code of 200. The same record set shows a PageSpeed performance score of 92, measured on 2026-09-17.
Recorded Evidence
The domain docuposte.secure-mailing-service.com was first observed on 2026-09-17. VirusTotal recorded 14 detections across 91 scanners on 2026-09-29. The SSL certificate was issued by Let's Encrypt / YR2, scanned on 2026-09-17. The PhishDestroy internal catalogue listed the domain, with the blocklist check dated 2026-10-01.
Interpretation
The HTTP 200 response and the PageSpeed score describe separate measurements taken on different dates, so they should be read as distinct records rather than a combined signal. The VirusTotal figures and the PhishDestroy catalogue entry come from different sources with different collection methods, and neither should be treated as a conclusion about the domain. The first-observed date and the certificate scan share a calendar date, which does not by itself establish that the observations were made at the same moment.
Recommended Actions
Preserve the HTTP response record and the VirusTotal detection record for docuposte.secure-mailing-service.com, since they can be compared against later checks. Keep the PhishDestroy catalogue entry and the PageSpeed score as separate records, and compare each against future observations of the same source. Review the full domain docuposte.secure-mailing-service.com against these preserved records before deciding on any further handling.
Certificate hostname mismatch·
颁发者 Let's Encrypt / YR2· stored validity ends in 60 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
20.50.64.14
Network ASN
AS8075
Organization
Microsoft Azure App Service (northeurope)
Observed location
Dublin, IE
Server header
Microsoft-IIS/10.0
域名服务器 2
ns1-32.azure-dns.com
ns2-32.azure-dns.net
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt / YR2
Valid from
2026-09-11 23:56:53
Valid until
2026-12-10 23:56:52
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-17 04:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint81266f8a470c6693216cc05bf5b1dc3074e631f66efce89add675ce6bd72be2dCertificate names · 1 SANs
secure-mailing-service.com
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:08:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:08:38 UTClast content: 2026-10-11 10:08:38 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.
技术 · 2 identified
W
Windows Server
Operating systems
Windows Server is a brand name for a group of server operating systems.
Google PageSpeed Insights — mobile performance audit of docuposte.secure-mailing-service.com· checked Sep 17, 2026
92
Good
Performance
FCP
2.5s
First Contentful Paint
LCP
2.92s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.5s
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-17 04:28:32 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-17 03:30:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 20.50.64.14.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
10 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
