Skip to content
Benchmarks

redact-secret · Report

Public validation key (pubkey-)

pubkey- followed by 32 bytes; Mailgun's public email-validation key, not a secret.

  • Mailgun
  • Detectors: none mapped
  • Run 2026-10-07
  • Mode published · redact-secret 0.1.0-beta.14
All providers
  • Dossier verdictRejected
  • Dossier evidence levelNot recorded
  • Dossier researched2026-09-29
Documented public per redact-secret#314's scope; gitleaks 8.30.1's mailgun-pub-key rule still flags it, which the mailgun-api-key public-id control records.

Research record

From credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0. It describes the research on the format, not what any scanner or the product does, and not a support status.
  • Review stateDraft, not reviewed
  • Format revision1 · proposed, none current
  • ResearchRejected
  • Researched2026-09-29

2 events in the review history: 1 observed, 1 reviewed. Latest: observed on 2026-09-29 by automation, project maintainer. Project-maintained review is not independent validation. The family record at this release.

Format

Provider format research from credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0.

What it looks like

Shape not recorded.

Format facts

Open questions

No open question is recorded for this revision.

Benchmark dossier notes

From the provider dossier, as written. The evidence level above says how well the format is backed; a fact the dossier does not record is not shown.
Shape
never stated by Mailgun. The prefix pubkey- comes from mailgun-python's log filter ((key-|pubkey-)[\w\-]+, described as scrubbing "Mailgun private and public key patterns"), mailgun-ruby's recorded regenerate-key response (a pubkey- placeholder) and a 2018 customer report. pubkey- + 32 lowercase hex comes from gitleaks (mailgun-pub-key, behind a mailgun keyword) and about thirty tools that copy it or its ancestors (betterleaks, Checkmarx 2ms, semgrep-rules, PEASS-ng, gitGraber, ScoutSuite). trufflehog, Nosey Parker, CredSweeper and detect-secrets have no pubkey- rule. The #582 measurement found 17 pubkey- + 32 candidates in public code, 16 of them hex-only.

In this benchmark

Fixture rows on the current run. Counts are for redact-secret in published · redact-secret 0.1.0-beta.14 mode.

No fixtures in this family yet

Nothing in the corpus targets it, so nothing is measured and no coverage is claimed.

Not measured

Scanner rules for this family

Mapped by hand (reviewed 2026-09-30) from each scanner's pinned rule file, never from what a scanner found on the fixtures.
Peer scanner rules that target this family
ScannerRuleWhat the rule matches
gitleaks · rules 8.30.1mailgun-pub-keymailgun keyword + pubkey- + 32 hex

No rule maps to this family in flare-redact, openredaction, trufflehog.

0 of 0 rows

No fixtures in this family yet

Nothing in the corpus targets it, so nothing is measured and no coverage is claimed.

Not measured

Sources

Researched 2026-09-29.

Documentation and code

  • github.com/gitleaks/gitleaks/blob/v8.30.1/config/gitleaks.toml
  • help.mailgun.com/hc/en-us/articles/360010523074-Email-Validations
  • help.mailgun.com/hc/en-us/articles/203380100-Where-can-I-find-my-API-keys-and-SMTP-credentials
  • github.com/mailgun/validator-demo/blob/2c0f9731d26c35ea9fd257979342fc77c5fd38e9/index.html
  • devcenter.heroku.com/articles/mailgun-validations
  • github.com/mailgun/mailgun-ruby/issues/145
  • github.com/mailgun/mailgun-python/blob/ce47f6bb7c9035d2c8070a9cf2c2e1a57eb5b40a/mailgun/filters.py
  • github.com/gitleaks/gitleaks/blob/b58d3f102cf3a2c84cb7f923d05c25c9b1aed84b/config/gitleaks.toml
  • docs.gitlab.com/user/application_security/dast/browser/checks/798.73/

Research log

Other Mailgun families