Language: EN

Domain health

What the checks mean, and what it takes to turn them green. More settings are under Technical info.

1

How a domain name is built

Names and labels

Domain name
A name in the DNS hierarchy, made of labels.
Label
One part between the dots, at most 63 octets in DNS wire format.

Levels

Top-level domain (TLD)
The label closest to the root. Country codes are ccTLDs, most others gTLDs.
Second level (SLD)
The name part right before the top-level domain.
Registrable domain name
Registered through a registrar under the top-level domain's rules. For .no, Norid runs the registry.

Below the domain

Subdomain
A name below another. Can live in the same zone or be delegated, and is usually not registered separately.
Parent domain
The name directly above another. Not necessarily a separate zone.
FQDN
All labels up to the root. The absolute form ends with the root dot.

Zone

DNS zone
Part of the DNS hierarchy administered as one unit.
Apex
The top of a zone, where the SOA and NS records live.

The number of dots does not decide whether a name can be registered: gloppen.kommune.no is registered at the third level under Norid's category domain kommune.no.

2

Reading the score

Colours

The share of checks that are in order.

Green
90–100 %
Orange
50–89 %
Red
Below 50 %
Light green
Half a point: DMARC with p=none, see DMARC
Grey
Does not count for this domain

Grey is a missing MX, DKIM when SPF authorises no senders and no DKIM exists, DNSSEC awaiting check, expiry with no known date, and DNSSEC and expiry for subdomains. See Subdomains for DMARC.

Updates

When a change shows up.

The asset
Right away
List and dashboard
Within 15 minutes
DS in the parent zone
Measured every night

The checks read the DNS records in the zone at Kleri. DNS hosted elsewhere is not measured.

3

DNSSEC

DNSSEC Kleri

DNSSEC authenticates DNS data and helps protect against tampering with DNS responses.

DNSSEC active
The DNS zone is signed, and a DS record is published in the parent zone. For .no, DS publication goes through the registrar to Norid.
DNSSEC not activated
DNSSEC can be activated for the domain. Signing and DS publication must be completed correctly.
DS record missing
The DNS zone is signed, but the DS record is missing in the parent zone. Complete the publication to establish the chain of trust.
DNSSEC validation may fail
A DS record exists in the parent zone, but the DNS zone is not signed. Validating resolvers may return SERVFAIL. Contact Kleri.
Awaiting check
The zone was recently signed and has not been checked yet. Counts neither for nor against until the next check.

For .no, DS records are published through the domain's registrar to Norid. DNSSEC status is checked periodically. After changes, the status may be undetermined until the next check.

4

SPF

SPF DNS zone

SPF specifies which senders are authorised to send e-mail on behalf of the domain.

Checks
A TXT record for the domain starting with v=spf1. The domain must have one SPF policy per name.
With e-mail
Add the SPF policy your e-mail provider recommends. Include every legitimate sender, including web forms, CRM systems and newsletter tools.
Without e-mail
If the domain should not send e-mail, SPF can be set to v=spf1 -all. Also consider DMARC with p=reject to protect the visible From address against spoofing.

E-mail at Kleri (standard example): v=spf1 include:_spf.straumpost.no -all

Microsoft 365 (standard example): v=spf1 include:spf.protection.outlook.com -all

Google Workspace (standard example): v=spf1 include:_spf.google.com ~all

Without e-mail: v=spf1 -all

The standard examples must be checked against the customer's actual e-mail setup. Publish only one SPF policy per domain name. Several e-mail providers must be combined in one policy. SPF has a limit of 10 DNS lookups, so check the policy before publishing.

5

DKIM

DKIM E-mail provider

Signs outgoing e-mail, so the recipient can check that it comes from the domain and was not changed on the way.

Checks
At least one DKIM record on a selector-specific name, for example selector1._domainkey.example.no. The record can be TXT or CNAME, depending on the provider. Or _domainkey is delegated to a DKIM service with NS, for example PowerDMARC Hosted DKIM.
Counts
When the SPF policy allows senders to send e-mail for the domain, or DKIM is already set up. Not based on MX.
Fix
Turn on DKIM at every sender (e-mail provider, newsletter, CRM), and add the records it gives you to the DNS zone.

Microsoft 365: usually two CNAME records, selector1._domainkey and selector2._domainkey. Google Workspace: usually one TXT record, google._domainkey. Always take selector names and target values from the provider's own configuration.

Sending via straumpost: two CNAME records, straumpost1._domainkey and straumpost2._domainkey, pointing to <domain>-1.dkim.straumpost.no and <domain>-2.dkim.straumpost.no, with dots replaced by hyphens (customer.no becomes customer-no-1). We create them when DNS is with us.

6

DMARC

DMARC DNS zone

DMARC lets the recipient check whether SPF or DKIM passes and aligns with the domain in the visible From address, and states which policy to apply on failure.

Checks
A TXT record at _dmarc.<apex> starting with v=DMARC1, or a CNAME to a DMARC service.
Points
Full point with p=quarantine or p=reject. With p=none, DMARC gives half a point: the record is set up, but the recipient does nothing with e-mail that fails, and external checkers report that the policy is not enabled. For subdomains, sp= applies when present.
With e-mail
Start with p=none and a report address. Use the reports to map legitimate senders and fix errors, then tighten to quarantine and reject.
Tighten
If the domain only sends through known services, such as Kleri or Microsoft 365: send a test e-mail to a Gmail address, choose “Show original” and check that SPF, DKIM and DMARC say PASS. Then set p=quarantine, and later p=reject. If the domain has many or unknown senders, find them first through the reports or a DMARC service such as PowerDMARC.
Without e-mail
If the domain does not send e-mail, and no legitimate system uses the domain in the From address, p=reject can be used from the start.

Name: _dmarc

Start: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com The rua address must be valid and able to receive the reports.

Without e-mail: v=DMARC1; p=reject;

7

Expiry

Expiry Kleri

Kleri renews the domain automatically until it is cancelled.

Renews automatically
The domain has not been cancelled. The date is the next renewal.
Expires in N days
The domain has been cancelled and will not be renewed. Red under 30 days.
Unknown
The registration date is missing. Does not count.

No action needed to keep the domain. If you cancelled it and changed your mind, contact Kleri before it expires.

8

MX

MX Info

Shows where e-mail for the domain is delivered. Not counted in the score.

Set up
The domain receives e-mail through the servers in its MX records.
No MX
Senders try the domain's A/AAAA record instead (implicit MX). A missing MX says nothing about whether the domain sends.
Null MX
MX 0 . explicitly states that the domain does not receive e-mail (RFC 7505).

For domains that should not send e-mail, v=spf1 -all and DMARC with p=reject are policies against unauthorised use of the domain. They do not follow from the MX record.

9

Subdomains

Subdomains

A subdomain delegated to its own DNS zone, for example asp.idrift.no. Names that live in the parent zone are part of that zone and are not measured separately.

DNSSEC
For a delegated, signed zone, the DS record is published in the parent zone, not at the registrar. Does not count here.
Expiry
Follows the registered domain the delegation depends on. The subdomain is not a separately registered domain and does not count.
DMARC
A _dmarc record on the subdomain is used when it exists. Otherwise policy discovery follows the organisational domain, including any sp= policy. If the parent domain is not hosted at Kleri, the inherited policy cannot be read and DMARC does not count.
SPF and DKIM
Domain health looks for records on the subdomain. The recipient evaluates SPF against the envelope sender domain and DKIM against the signing domain (d=), which may be a different name.
10

Want Kleri to sort it out?

Contact us

Include the domain and which checks are missing.

E-mail
hei@kleri.no
Phone
+47 48 08 88 00 Weekdays 08–16
Support
kleri.com/support