Skip to main content
WEBHOOK

Authorizations

Authorization
string
header
required

Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic <base64(username:token)>' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com.

Headers

X-NAMECOM-SIGNATURE
string
required

HMAC signature for the request payload. See HMAC signing documentation for verification details.

Body

application/json

Payload sent when a registry reports that a domain must remediate a policy compliance issue before a deadline. By default, name.com emails the registrant; subscribing replaces that email so you can notify the end user from these fields. If you have signed an addendum to assume all email responsibility, name.com does not send the email and this webhook is the only delivery path. Whitelabeled branding is applied to the email when your account has it configured.

eventName
enum<string>
required

The name of the subscription event.

Available options:
domain.registry.compliance_notice
domainName
string
required

The domain subject to the registry compliance notice.

Example:

"example.new"

policy
enum<string>
required

Stable, namespaced identifier for the registry policy requiring remediation. Branch on this value rather than any human-readable field.

Available options:
new_resolves_within_100_days,
new_used_for_action,
new_account_for_review
policyName
string
required

Human-readable name of the registration policy associated with the compliance requirement.

Example:

".NEW Domain Registration Policy"

policyUrl
string<uri>
required

URL of the registration policy associated with the compliance requirement.

Example:

"https://www.registry.google/policies/registration/new/#!/"

registryName
string
required

Human-readable name of the registry that issued the compliance notice.

Example:

"Example Registry"

issueDescription
string
required

Human-readable explanation of the compliance issue identified by the registry. Suitable for forwarding to the registrant. The wording may change; do not branch on this text.

Example:

"The registry determined that the domain does not resolve to an action within 100 days of registration."

remediationInstructions
string
required

Human-readable instructions for resolving the compliance issue. Suitable for forwarding to the registrant. The wording may change; do not branch on this text.

Example:

"Configure the domain to launch an online creation or action-generation flow, and ensure the website is accessible using an active SSL certificate."

agreementReminder
string
required

Human-readable reminder that the registrant agreed to the applicable registration policy. Suitable for forwarding to the registrant. The wording may change; do not branch on this text.

Example:

"As a reminder, when you registered this domain, you agreed to the .NEW Domain Registration Policy, which includes this requirement."

noncomplianceConsequences
string
required

Human-readable explanation of what the registry may do if the issue is not remediated by complianceDeadline. Suitable for forwarding to the registrant.

Example:

"If the website is still not compliant by the deadline, the registry may suspend or cancel the domain. Suspended domains do not resolve and cannot be transferred or deleted."

contactInstructions
string
required

Human-readable instruction for the registrant to contact the registry (not the registrar) if they believe the domain is compliant or need to submit evidence. Suitable for forwarding.

Example:

"If you believe the domain is compliant or need to submit evidence, contact the registry."

complianceDeadline
string<date-time>
required

The deadline by which the compliance issue must be remediated.

Example:

"2026-10-25T15:30:00+00:00"

remediationPeriodDays
integer
required

The remediation period supplied by the registry, in days.

Required range: x >= 0
Example:

45

registryEmail
string<email>

Registry mailbox for evidence and questions, when the registry publishes one. Include it in the message body when notifying the registrant. Omitted when the registry does not publish a contact address.

Example:

"compliance@registry.example"

originalMessageId
string

RFC 5322 Message-ID of the registry's original notice, when available. Omitted when the registry notice had no Message-ID.

Example:

"<notice-12345@registry.example>"

Response

The subscribed server accepted the request.