Inspect DNS observations relevant to receiving email and sender authentication.
An explicit check sends your domain and optional selector to Roled's server. DNS queries reveal those names to the configured resolver and potentially downstream authoritative DNS services. This is not browser-local.
No email is sent, no mailbox is checked, and no SMTP or HTTP connection is made to the entered domain. Results are a configured-resolver snapshot, not deliverability, spam, security or compliance certification.
Check a domain
For example, example.com or mail.example.org. Use ASCII or a valid punycode A-label. One trailing root dot is accepted. Enter a domain, not a URL, email address, IP address or port. No spaces or internal/reserved names.
For example, default, selector1 or march.eu. Enter only the selector. The server constructs selector._domainkey.domain; complete query names must fit DNS length limits. Selectors are never guessed. Without one, DKIM is not checked.
Checks use bounded MX/TXT lookups, A/AAAA fallback when appropriate and an optional selector TXT/CNAME observation. No SPF recursion, reporting-URI fetch or CNAME-chain follow-up. Reset or edits ignore old results; they do not prove server DNS work stopped.
Email DNS observations
MX
SPF
DMARC
DKIM
Review the summary before sharing. Full DKIM public-key material is omitted. A copied observation is not proof that messages authenticate or reach an inbox.
Limits of DNS-only checking
Lookup failure is different from a successful response containing no requested records. Empty answers do not establish NXDOMAIN, DNSSEC validation or authoritative global truth. Native DNS calls can block according to resolver settings.
MX or fallback addresses do not prove an SMTP listener exists. SPF is not recursively evaluated. Only exact-name DMARC is inspected; organisational-domain inheritance is not evaluated. A DKIM key observation is not structural key or signature verification. Receiver behaviour and actual signing are untested.
The tool saves no query history in Drupal or browser storage. Normal Drupal admission records, hosting/security logs and resolver infrastructure remain separate. Page exit clears held results without promising secure memory erasure or isolation from other page scripts/extensions. Previously initiated clipboard writes cannot be recalled.