Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ovh.net.
The latest stored availability evidence still shows the domain reachable; 29 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.
xn--myledgr-oya[.]com
“Site en construction”
The domain xn--myledgr-oya.com was registered on July 15, 2026 through OVH, SAS and is currently served by the nameservers dns106.ovh.net and ns106.ovh.net. DNS resolution points to the IP address 213.186.33.5, which is part of OVH infrastructure. VirusTotal reports that two of ninety‑one security vendors have flagged the domain, indicating that at least a small subset of scanners have identified malicious characteristics. The domain is classified as a generic_phishing threat with a high risk rating and remains active as of the report date. Publicly available intelligence does not include a detailed page analysis, so the exact phishing content, targeted brands, or credential‑harvesting mechanisms are unknown. Defenders should treat the domain as hostile: block DNS resolution and HTTP traffic to xn--myledgr-oya.com, add the IP 213.186.33.5 to network‑level deny lists, and monitor for any related activity originating from the same OVH name‑server set. Continuous re‑evaluation is advised, as additional detections may emerge if the site begins serving more observable payloads.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
VirusTotal Analysis
Evidence & External Reports
PD-20260718-CCB80F Recipient: abuse@ovh.net Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive