🇺🇸English

Strategy: Brand Protection

Guides discovery, reporting, and prevention of brand impersonation—fake websites, phishing sites, trademark infringement, and domain squatting. See domain-selection for defensive domain registration; trust-badges for official site verification signals; about-page for identity declaration.

When invoking : On first use , if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand name, official domain, and key assets.

Identify:

1. Impersonation type : Fake website, phishing, trademark misuse, domain squatting
2. Evidence available : Screenshots, URLs, WHOIS, hosting info
3. Legal assets : Registered trademark, copyright ownership
4. Impact : Traffic interception (fake site ranks for brand queries)? Payment fraud (users pay on fake site, then contact official support)?

Evidence Collection Checklist

Reporting Channels (Priority Order)

Report content : Include full URL, clear description of fraudulent activity, and all evidence (screenshots, logs).

Reporting Best Practices

Registrar vs hosting : Use ICANN Lookup for registrar. For hosting, use IP lookup (HostingCheckerOnline, HostingDetector, ipinfo.io) to find origin server—registrar may be Cloudflare while origin host is elsewhere; report to both.

Cloudflare as registrar : Use abuse.cloudflare.com or abuse form; select "Phishing & Malware" for impersonation. Email complaints are generally not processed; use the online form. Provide specific URLs of infringing pages.

Hosting detection : Sites behind Cloudflare CDN hide origin IP. Use reverse IP lookup or hosting detection tools to identify underlying host; submit abuse to that provider as well.

Parallel reporting : Submit to registrar, host, and Google Safe Browsing simultaneously; do not wait for one before others. Google trademark review takes 1–8 weeks.

Legal Options

Prevention Measures

Defensive Registration

• Register brand+ai, brand+app, brand+official, etc. See domain-selection for defensive registration.
• Redirect variants to main domain; do not deploy separate sites.

Official Site Verification

Place "Official website: [domain]" prominently:

• Homepage (above fold or hero)
• Sign-in / Sign-up pages
• Pricing / Payment pages : "Only pay at [official-domain]. Do not enter payment on other domains."
• Footer : "© [Brand]. Official site: [domain]"
• FAQ : "How do I verify I'm on the official site?" → "The only official URL is [domain]. Any other domain is not affiliated."

Use trust-badges for verification signals. See about-page for identity declaration.

Customer Support (Payment Fraud)

When users report "can't use after payment" but no record exists—likely paid on fake site:

1. Verify source : Ask which URL they used (request screenshot or URL).
2. Response template : Explain that the only official site is [official-domain]; if they paid elsewhere, that site is not affiliated. Recommend: (a) dispute charge with payment provider, (b) use only [official-domain] going forward.
3. Roll out template to support team; ensure consistent messaging.

User Education

• Social media pinned post / announcement: "Only use [official-domain]"
• Email signatures, support replies: link to official domain only

Traffic Recovery (When Impersonation Intercepts Search)

Monitoring (Ongoing)

• Periodic search: brand name + common variants (e.g., brand+ai, brand+app)
• See brand-monitoring for monitoring setup, tool selection, and cadence

Timeline (Typical)

Implementation Checklist

Short-term (1–2 weeks) : Evidence collection; abuse reports to registrar and host; Google Safe Browsing report; DMCA if applicable; add "Official website" on site.

Medium-term : Add impersonation guidance to domain-selection; official verification to trust-badges, about-page.

Long-term : Periodic search (brand + variants); brand monitoring (BrandShield, Doppel); defensive registration of variants.

Output Format

• Evidence package (checklist, evidence list)
• Report templates (registrar, hosting, Google)
• Timeline (immediate vs medium vs long-term actions)
• Prevention (defensive registration, site verification, user education)

References

• How to Report and Take Down a Fake Website - LegalClarity
• Website Spoofing: Detection and Take Down - BrandShield
• ICANN DNS Abuse Complaints Guide
• Google Safe Browsing - Report Phishing
• Cloudflare Abuse Reporting — use online form; select Phishing & Malware
• Google Trademark Complaint
• Bing Content Removal

Related Skills

• domain-selection : Defensive domain registration; brand variants
• rebranding-strategy : When rebranding, sync brand protection checks
• brand-monitoring : Proactive monitoring setup; tool selection; this skill = reactive takedown
• branding : Brand asset protection; consistency
• trust-badges : Official site verification signals
• about-page : Official identity and domain declaration
• homepage-generator : "Official website" placement
• google-ads , paid-ads-strategy : Brand search ads for traffic recovery
• schema-markup , title-tag : SEO for branded queries

Weekly Installs

158

Repository

kostja94/market…g-skills

GitHub Stars

237

First Seen

Mar 6, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

cursor145

github-copilot144

gemini-cli144

kimi-cli144

codex144

opencode144