Domain registrar credentials

Identifies domain registrar credentials patterns in security and access control contexts. Detects potential exposure of sensitive security information in international systems.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.

Detection quality

Mixed

Jurisdictions

global

Regulations

GDPR

Data categories

credentials, security

Scope

wide

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:domain\s+registrar|registrar\s+credentials|domain\s+login|domain\s+transfer|EPP\s+code|auth\s+code|domain\s+renewal|registrar\s+account)\b

Corroborative evidence keywords

domain registrar credentials, domain, registrar, credentials, operations, resilience, api key, api_key, apikey, access key, access token, auth token, authorization, bearer, conn str, connection string, connectionstring, cookie, credential, database (+43 more)

Proximity: 300 characters

Should match

• domain registrar — Primary topic phrase match
• registrar credentials — Case-insensitive topic phrase match
• domain login — Alternative topic phrase match
• domain transfer — Additional topic phrase match

Should not match

• unrelated generic text without domain phrases — No relevant topic phrases present
• placeholder value 12345 — Random text should not match topic-specific regex
• backup outage — Generic word pair from old broad template should not match

Known false positives

• Authentication-related terminology in software documentation, security training materials, or system architecture descriptions without actual credentials. Mitigation: Require proximity to credential-specific patterns (API keys, connection strings, tokens) rather than general security terminology.
• Code snippets and configuration examples containing credential-related keywords or placeholder values in developer documentation. Mitigation: Check for common placeholder patterns (example.com, localhost, 0000) and documentation file types to reduce false positives from technical writing.