Dataweaz

wnf.nl

Summary

Registrar
—
Status
active
Created on
July 7, 1996
Expires on
—
Name servers
nsauth2.bit.nl, nsauth1.bit.nl, nsauth3.bitnl.eu
Mail servers
wnf-nl.mail.protection.outlook.com
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from wnf.nl but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
[email protected]

Record

v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1;

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for wnf.nl.

RuleValueResult
includespf.protection.outlook.comAllowed
ip4213.75.3.23Allowed
ip489.188.1.89Allowed
includespf.xsdirect.nlAllowed
all—Rejected

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:spf.protection.outlook.com ip4:213.75.3.23 ip4:89.188.1.89 include:spf.xsdirect.nl -all

E-mail signing (DKIM)

DKIM keys published by wnf.nl under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 1024 bits · shortActive
selector2Microsoft 365RSA 2048 bitsActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to wnf.nl arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from wnf.nl was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @wnf.nl address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

wnf.nl  MX  10 mx1.wnf.nl.
wnf.nl  MX  20 mx2.wnf.nl.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.wnf.nl.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

wnf.nl  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.wnf.nl, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.wnf.nl  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.wnf.nl, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.wnf.nl  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of wnf.nl

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

TypeIP address
A217.114.94.2

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
nsauth2.bit.nl213.136.12.59
nsauth1.bit.nl213.136.12.51
nsauth3.bitnl.eu85.17.15.88

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @wnf.nl addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10wnf-nl.mail.protection.outlook.com52.101.103.137

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.wnf.nl.

NameContent
wnf.nlv=spf1 include:spf.protection.outlook.com ip4:213.75.3.23 ip4:89.188.1.89 include:spf.xsdirect.nl -all
wnf.nlt80db9trtbvrstnxng61zgc1yxm3scbl
wnf.nlfacebook-domain-verification=2lhf4bs6e3yxgeq8ciscbpcc1sm172
wnf.nlVmHSUI77A1aLQAmZFrBXlUqiKAZdAVW47EL4qAKtKgM=
wnf.nlWereld Natuur Fonds (14078) (33885)
wnf.nlmonday-com-verification=Fza7OiMsouKMayA7vEhBY27YH17jdofbYeuPPwuq2KQ
wnf.nlatlassian-domain-verification=JJlt01/OfvXr0HsX23NZzSjJNdM41z7oszWYfT4Yvkxdt2Ui+XdbmAYYLH+sLQPa
wnf.nl_ist28vdejmc8wu6l50ntuku336a3lq9
wnf.nlMS=ms87194028
wnf.nlapple-domain-verification=GtWhrrW1CvWsqosS
_dmarc.wnf.nlv=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1;
selector1._domainkey.wnf.nlv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXfFbHQ4TBP7I1qbN/+4IqsgdGSD/ZCZmxwxAvz22J00GXD6dR5/CAi6brHMW6rcQ/6yCe2R0vRq16CkZeo2sS3vTXYc8rZ7Z0IDpt1UrxG2ZyrQ02cWPf0Sh/MtoEf8F3nzFxwsy37YzugWgiSN764PrP/KoRnHzVUc54EB4/pwIDAQAB; n=1024,1450328269,1466139469
selector2._domainkey.wnf.nlv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwdTQwwWqLU+KXEJLHIhZwkipZWO4zSxwffXsezHCqPTEMgaCZw6eTy1Mnh9hHU2BFxU0AG2IxXXkSyoKYYGe30S1f+wLg9bMnF1Rri+1YvxtRzKYliahqv4Y0Vk1aEqSbNHPGyK3y7w9adFkzNO/5PE1vVwiiOB9548ptN0ypl0hcao60e87BQMkzyT9qXEz656mzHpo5dYWCCyUj6kKZxty1cpIX1DaDPsGILdi7od8+HZslFMZ4fcdIzguy0O1+gqPG/h5wVuihD8k3Zk8yxV5O7TzFoNdfznX0EjFYwACL34PdS3hV7fiuhcFSPkHGf2/0cYdQHO/FiNBbiFvXQIDAQAB;

Related IP addresses

IPv4 addresses used by wnf.nl: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
217.114.94.2Website217.114.94.0/24
213.136.12.59Name server nsauth2.bit.nl213.136.12.0/24
213.136.12.51Name server nsauth1.bit.nl213.136.12.0/24
85.17.15.88Name server nsauth3.bitnl.eu85.17.15.0/24
52.101.103.137Mail server wnf-nl.mail.protection.outlook.com52.101.103.0/24
213.75.3.23Authorized by SPF213.75.3.0/24
89.188.1.89Authorized by SPF89.188.1.0/24

WHOIS of the domain wnf.nl

Domain name: wnf.nl
Status:      active

Registrar:
   BIT B.V.
   Galileilaan 19
   6716BP Ede Gld
   Netherlands

Abuse Contact:
   +31.318648688
   [email protected]

DNSSEC:      yes

Domain nameservers:
   nsauth1.bit.nl
   nsauth2.bit.nl
   nsauth3.bitnl.eu

Creation Date: 1996-07-07

Updated Date: 2026-06-26

Record maintained by: SIDN BV

% Query time: 238 msec
% WHEN: Fri Oct 02 14:51:59 UTC 2026