Skip to security report
Domain security and threat intelligence
men2020.company favicon

men2020.company

“MEN”

Threat verdict Critical 81/100 evidence score
Availability Last known active Latest stored reachability observation
VirusTotal detections: 1/91 Brand impersonation: ["gmail"] Last known active
OTX: 4 refs Sep 26, 2026 ["gmail"] 1 Report Sent CDN
Actions API
⚠️
This domain has been flagged as malicious
Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ 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@name.com. The latest stored availability evidence still shows the domain reachable; 25 hours 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.

Elapsed since first report
25 hours
Reports sent
1
Latest case ID
PD-20260926-0CBB5D
Current status
HTTP 200 at latest stored check

Evidence Summary

CRITICAL
Score
81/100

Assessment
Stored evidence for men2020.company: VirusTotal recorded 1 detections among 91 scanners on 2026-09-27. That ratio reproduces the stored check in its original units and is not converted into another measure. PhishFeed appear as named external blocklist observations for men2020.company. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence
VirusTotal records 1 detections among 91 scanners in the stored snapshot dated 2026-09-27. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-27 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context
PhishFeed are recorded as named external blocklist observations for men2020.company in the snapshot dated 2026-09-27. The stored PhishFeed blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains men2020.company as a publisher record. That PhishDestroy record is counted separately from the PhishFeed external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline
The record first observed men2020.company on 2026-09-26. The PhishFeed blocklist snapshot is dated 2026-09-27 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for men2020.company on 2026-09-27. The HTTP status 200 dated 2026-09-27 records a single response for later comparison. The registration date is separately recorded as 2026-06-21. A URLScan reference was stored on 2026-09-26 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure
The source stores 64.29.17.1 as the observed address in this record. The registration date for men2020.company is recorded as 2026-06-21. The SSL issuer is recorded as Let's Encrypt / YR2 in the snapshot dated 2026-09-26. The stored ASN observation records 16509 in this record. The observed server header is recorded as Vercel in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion
The men2020.company record states that VirusTotal recorded 1 detections among 91 scanners on 2026-09-27. PhishFeed remain named blocklist observations from the snapshot dated 2026-09-27. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 64.29.17.1. The supported conclusion is bounded to the exact stored observations for men2020.company. Any statement beyond those source values would require additional dated material.

Recommended Actions
Avoid submitting sensitive information to men2020.company during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain men2020.company as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and PhishFeed blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to men2020.company. The stored record does not justify extending that rule to 64.29.17.1 or to other infrastructure records.

VirusTotal
VirusTotal
1 det.
OTX references
URLScan
URLScan
TLS Certificate
Let's Encrypt / YR2
Age
3 mo
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed
Reports Sent
1
Data coverage VirusTotal 1 / 91 URLQuery report stored — detailed verdict pending OTX 4 community references CF Radar scan completed URLScan capture stored report URLScan verdict Analysis completed TLS valid certificate, 55d WHOIS 3 mo old Screenshot 2 captures · 2 sources

Forensic History & Detection Timeline

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.
  1. VirusTotal Detections Update Sep 27, 2026 · 04:07 UTC
    VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: Forcepoint ThreatSeeker.
  2. Threat First Observed Sep 26, 2026 · 10:30 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 64.29.17.1.

Threat Response Pipeline

Discovery
Checks
Reports
Availability
13/14
Sent Report Recorded
Stored sent-report record for registrar Name.com, Inc., hosting provider, 2 abuse contacts
abuse@name.comabuse@vercel.com
Sep 26, 2026

Public Blocklist Status

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Vercel

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Vercel

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 2 sources

Page Title
MEN
Impersonates
Gmail
TLS Certificate
Valid transport encryption · Issued by Let's Encrypt / YR2 · valid for 55 days

Domain Intelligence

Domain
URLScan Verdict Analysis completed score 0 report ↗
Server / ASN Vercel · AS16509 Amazon.com, Inc.
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX Tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Name.com SE(SE)
IP Address 64.29.17.1 CDN
GeoUS Walnut, US
NetworkAS16509 · Vercel, Inc
The origin IP is hidden behind a CDN proxy. Reverse-IP results for the edge address contain unrelated tenants; finding the origin requires passive DNS or certificate-transparency data.
RegistrationCreated Jun 21, 2026 (98d) — Expires Jun 21, 2027
HTTP Status200
Technical detailsDNS, SSL SANs, timestamps
First DetectedSep 26, 2026
DOM Analysisanalyzed Sep 26, 2026score 81/1001 brand signal
IoC Extractionscanned Sep 27, 20260 wallet · 0 Telegram IoCs
Submitted URLhttp://men2020.company/
Nameserversns1.vercel-dns.comns2.vercel-dns.com
TLS Fingerprint
TLS Observationvalid from Aug 23, 2026scanned Sep 26, 2026
Favicon Hash
Case ID
ICANN OVERSIGHT

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.

Accountability draft Nothing is sent automatically.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of men2020.company · checked Sep 26, 2026

65
Needs Work
Performance
FCP
4.06s
First Contentful Paint
LCP
5.11s
Largest Contentful Paint
CLS
0.02
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
8.31s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260926-0CBB5D Recipient: abuse@name.com
Page title stored with report: MEN
URLScan evidence VirusTotal evidence URLQuery evidence Screenshot 686.4 KB
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.

Were You Affected by This Site?

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Europol
Find the official reporting channel for your EU country
National police directory
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory
Template-based draft • optional AI wording assistance requires separate consent Review and submit it yourself

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/men2020.company"
  title="PhishDestroy threat report for men2020.company"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>