Notification and current-status evidence
The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 5 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
yesnoerror[.]xyz
“yesnoerror.xyz | 504: Gateway time-out”
Observation enregistrée
Contraste de titres observé
Résumé des preuves
This domain, yesnoerror.xyz, has been classified as a generic phishing site. The site returns an HTTP 403 response and a page title of “yesnoerror.xyz | 504: Gateway time-out”. VirusTotal records show that three out of ninety‑five security vendors have flagged the domain, and Gridinsoft assigns it a trust score of 0 out of 100. The domain appears on three external blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL, indicating that multiple threat‑intelligence feeds have identified it as malicious. The domain was registered on March 13, 2026 through Dynadot LLC and is serviced by Cloudflare nameservers uriah.ns.cloudflare.com and zara.ns.cloudflare.com. DNS resolution points to IP address 188.114.96.3, which belongs to AS13335 Cloudflare, Inc. and is located in the United States. The presence of Cloudflare and HTTP/3 suggests the operators are leveraging a widely used CDN to hide the origin server and to improve performance, a common technique in phishing infrastructure. Current analysis is limited to surface‑level indicators; the site returns a gateway timeout error and does not present a visible phishing payload at the time of observation. Consequently, the exact content, credential‑harvesting mechanisms, and target audience remain uncertain. The low number of vendor detections may reflect the recent creation date rather than a lack of malicious intent. Defenders should immediately block yesnoerror.xyz at network perimeter and endpoint controls, and add the associated IP 188.114.96.3 to deny lists. Continuous monitoring of DNS queries for the domain and its Cloudflare nameservers is advised to detect any future activation. Where possible, redirect traffic to a sinkhole or sandbox for deeper payload analysis, and share indicators of compromise with upstream threat‑sharing communities to improve collective detection.
Instantané des preuves transmises
- Envoyé
- Entrées du registre
- 1
- ID du dossier
PD-20260313-783D64- Titre de la page capturée
- Just a moment...
Fondement juridique
Texte intégral des preuves
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Data Coverage
Processus de réponse aux menaces Pipeline
Couverture des listes de blocage
10 sources externes surveillées · instantané du 11/08/2026
8 sources externes surveillées Aucune correspondance
Chronologie de détection
-
VirusTotal
0 → 2
Capture enregistrée
Informations sur les domaines
Détails techniquesDNS, noms TLS et horodatages
ICANN OVERSIGHT
Contexte de l’accréditation et du RAA
Contexte de l’accréditation et du RAA
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.
Analyse VirusTotal
Ce site vous a-t-il affecté ?
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Signalez-le à vos autorités locales
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Vérifier n'importe quel domaine
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignaler une tentative d'hameçonnage
Signalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerFlux d'alertes en temps réel
Rapports de phishing récents et changements de disponibilité observés
SurveillerRestez informés, restez en sécurité
Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif