VirusTotal
2 / 91
engines flag the domain
“Inicia sesion - MYDB.CC”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 22 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.
2 / 91
engines flag the domain
No threat flag
Not on Google threat lists at check time
No malicious flag
Browser scan with screenshot
0
threat pulses mention the domain
Online · HTTP 403
Cloudflare · 188.114.97.1 · TLS: Let's Encrypt
malicious
Each check shows its own collection time. Zero detections do not guarantee safety.
ब्लॉकलिस्ट में डोमेन: mydb.cc — अंतिम ज्ञात सक्रिय (HTTP 302). साक्ष्य सारांश: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
4 / 92 engine detections
रिपोर्ट खोलें2 det.
रिपोर्ट खोलें4 community references
रिपोर्ट खोलेंprovider verdict: clean
रिपोर्ट खोलेंNo threat flag
रिपोर्ट खोलेंNo malicious flag
रिपोर्ट खोलेंResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
mydb.cc is an impersonation phishing page that greets visitors with a Spanish-language login prompt titled "Inicia sesion - MYDB.CC", aimed at Spanish-speaking users who expect a legitimate account portal. PhishDestroy first flagged it on 2026-09-28. As of 2026-10-19 the domain is still live and responds with a redirect, so the threat remains active. The page title shows a login branded with the domain's own name rather than a recognizable third-party service, while our classification is impersonation phishing.
The "Inicia sesion" (sign in) heading is the core of the trap. It presents a familiar-looking account login so visitors type their username and password without hesitation. Whatever is entered goes straight to the operators, who can take over the account, reuse the same password on other services, or sell the credentials. Because the site now redirects, visitors may be bounced to a different page after the initial hit, which makes the lure harder to recognize.
Independent detection is still thin. On 2026-10-10 VirusTotal showed 4 of 92 engines flagging the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. Most scanners and browsers will therefore not warn a visitor yet. The domain appears in 4 AlienVault OTX threat pulses, so other researchers are tracking it too, and it is listed on the PhishDestroy blocklist.
The domain was registered through NAMECHEAP INC on 2024-05-14, more than two years before PhishDestroy caught it. That gap points to either a long-held domain later turned to phishing or a slow-burn operation that stayed under the radar. Traffic is fronted by Cloudflare, Inc. at an address geolocated to Canada, which hides the true origin server. A free Let's Encrypt certificate supplies the padlock icon. The padlock only means the connection is encrypted and does not show that the site is trustworthy.
If you entered credentials on mydb.cc, change that password immediately, along with any other account that uses the same or a similar password. Turn on two-factor authentication wherever possible. Then check recent sign-ins and active sessions on the affected accounts and log out any device you do not recognize. Watch for follow-up phishing emails or messages in Spanish that reference your account. Defenders should block mydb.cc at DNS and the web proxy, search logs for past visits and credential submissions, and force password resets for any users who reached it.
एज-आईपी प्रतिष्ठा इस डोमेन के लिए जिम्मेदार नहीं है।
everton.ns.cloudflare.commagdalena.ns.cloudflare.commx1.privateemail.compriority 10mx2.privateemail.compriority 10Location describes the IP network.
086aa1521c6ee7fd87f85abe305995852511d7b1237a4a2e303cea715a4df695Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.mydb.ccDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of mydb.cc · checked Sep 28, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
redirected→protected
cloudflare_challenge · Cloudflare · challenge
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
अज्ञात→redirected
http_redirect
2→3
3→2
2→3
पहुँच योग्य
No threat flag
View source4/92 engine detections
View source4 community references
View sourcePD-20260928-00FE01
Page captured
View sourcemydb.cc
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
mydb.cc
PD-20260928-00FE01 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
mydb.cc)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
संग्रहीत ब्लॉकलिस्ट, WHOIS, DNS और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंसंदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंहाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंलाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.