Dataweaz

dfv.de

Summary

Registrar
—
Status
connect
Created on
—
Expires on
—
Name servers
ns.plusline.de, ns.s.plusline.de
Mail servers
dfv-de.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 dfv.de but fails SPF and DKIM checks.

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

Record

v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s;rua=mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for dfv.de.

RuleValueResult
includespf.dfv.deAllowed
ip491.198.2.88Allowed
ip4185.233.188.231Allowed
ip4213.83.3.5Allowed
mxindivsurvey.deAllowed
include_spf.tivian.comAllowed
includecust-spf.exacttarget.comAllowed
includespf.protection.outlook.comAllowed
include_spf.pretix.euAllowed
include_spf.salesforce.comAllowed
all—Rejected

Top-level DNS lookups: 7 of 10 allowed

Record

v=spf1 include:spf.dfv.de ip4:91.198.2.88 ip4:185.233.188.231 ip4:213.83.3.5 mx:indivsurvey.de include:_spf.tivian.com include:cust-spf.exacttarget.com include:spf.protection.outlook.com include:_spf.pretix.eu include:_spf.salesforce.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive

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 dfv.de arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from dfv.de 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 @dfv.de 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

dfv.de  MX  10 mx1.dfv.de.
dfv.de  MX  20 mx2.dfv.de.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.dfv.de.
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

dfv.de  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.dfv.de, 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.dfv.de  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.dfv.de, 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.dfv.de  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 dfv.de

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
A5.75.140.122

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
ns.plusline.de212.19.48.14
ns.s.plusline.de212.19.40.14

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @dfv.de 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
10dfv-de.mail.protection.outlook.com52.101.103.140

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.dfv.de.

NameContent
dfv.dev=spf1 include:spf.dfv.de ip4:91.198.2.88 ip4:185.233.188.231 ip4:213.83.3.5 mx:indivsurvey.de include:_spf.tivian.com include:cust-spf.exacttarget.com include:spf.protection.outlook.com include:_spf.pretix.eu include:_spf.salesforce.com -all
dfv.deapple-domain-verification=1DT1M1cHQBAVEmX6
dfv.deatlassian-domain-verification=OpkmmmH/IhBASUj2iemReoyEPjxGxP5itzXQVVfcU4hYTE4tNeWf8PnNtKSruIOj
dfv.deSFMC-yDxZxKwk4MGGOmjNLjy4XuPVCAENTf5a4wbmzNTL
dfv.delogmein-verification-code=3257e032-f2eb-4a2c-8ff8-83fbca442a0a
dfv.deSFMC-XAAmEXmYsbWz7pjg8ol_IHtqj2g3kZHv44oXNIE0
dfv.de_edl9f7w7wc93785vx8vfzszt7pu98hk
dfv.deMS=ms17212358
dfv.demiro-verification=fc63f7b8774debcb27d361ffae162944a5b8189c
dfv.de_kjienl0hil3xuluyb48hglwhyki2imn
dfv.degoogle-site-verification=FdbUr1Y8wu0n4KCVYosCNtzOQqib-SNZox8iWZfC0HQ
dfv.deSFMC-VQsfD8REeg63bPPkMHBE0CvqG-zohNxl2RkpKCBt
dfv.dexsX34ElUlX6+qfPRrzTHZKD7F5bivWDipGMBJceRRx1pAYUNsxnPeAJ29HIhF9JA05UdZapD0+5jMAAsITKkeg==
dfv.deSFMC-5_4PSGZydKf_Y2Hs8Z04RcdtBMDSsgvWp74PHlaM
dfv.deatlassian-sending-domain-verification=af285d65-0a82-4c9d-96bd-5caff4de0fc6
dfv.degoogle-gws-recovery-domain-verification=47994913
_dmarc.dfv.dev=DMARC1;p=reject;sp=reject;adkim=s;aspf=s;rua=mailto:[email protected]
selector1._domainkey.dfv.dev=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzZ0+iizeQVyffDrKTerJB8dkUiq6ZMHvRE4Kb2ToRiC2C7IiZDBl+siW7jqQfFMXaVgyGugADe7H9+N1+5u5X1VEd42WadvGoGZ7OukzgEJtCH0FbJLYp4XCuv2It3EWOZTg2l5U55kpCDQJ7eB5xtCbFG2Ekn7cydZoCglu0/v12ZGVkuFDmAaheX78d9ddZfHTz+J/dacSRV78kxFKn+R4e6Y2KFDRh66+kOuwlCLrR5JpMEsuJ37/ie57RGfKDSdFpugo0bIdT/sK5+CnFLzsmFe+3R1aBi1qjQ5Yd1GXN+RPlm5SM3Rr1QMjja9tq3pdC14mZXGto+wvz8KJOQIDAQAB;

Related IP addresses

IPv4 addresses used by dfv.de: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
5.75.140.122Website5.75.140.0/24
212.19.48.14Name server ns.plusline.de212.19.48.0/24
212.19.40.14Name server ns.s.plusline.de212.19.40.0/24
52.101.103.140Mail server dfv-de.mail.protection.outlook.com52.101.103.0/24
91.198.2.88Authorized by SPF91.198.2.0/24
185.233.188.231Authorized by SPF185.233.188.0/24
213.83.3.5Authorized by SPF213.83.3.0/24

WHOIS of the domain dfv.de

Domain: dfv.de
Status: connect

% Query time: 333 msec
% WHEN: Fri Oct 02 10:59:58 UTC 2026