Dataweaz

smava.de

Summary

Registrar
—
Status
connect
Created on
—
Expires on
—
Name servers
ns-1295.awsdns-33.org, ns-1776.awsdns-30.co.uk, ns-931.awsdns-52.net, ns-105.awsdns-13.com
Mail servers
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
SPF
Soft

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

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

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

Record

v=DMARC1; p=quarantine; rua=mailto:[email protected]; sp=quarantine; pct=100

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

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

RuleValueResult
includespf0.smava.deAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:spf0.smava.de ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
mailjetMailjetRSA 1024 bits · shortActive
zendesk1ZendeskRSA 2048 bitsActive
zendesk2ZendeskRSA 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 smava.de arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from smava.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 @smava.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

smava.de  MX  10 mx1.smava.de.
smava.de  MX  20 mx2.smava.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.smava.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

smava.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.smava.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.smava.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.smava.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.smava.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 smava.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
A13.227.173.9
A13.227.173.112
A13.227.173.86
A13.227.173.121
AAAA2600:9000:21f7:2a00:2:80be:5a80:93a1
AAAA2600:9000:21f7:4200:2:80be:5a80:93a1
AAAA2600:9000:21f7:5a00:2:80be:5a80:93a1
AAAA2600:9000:21f7:6200:2:80be:5a80:93a1
AAAA2600:9000:21f7:9a00:2:80be:5a80:93a1
AAAA2600:9000:21f7:1e00:2:80be:5a80:93a1
AAAA2600:9000:21f7:6c00:2:80be:5a80:93a1
AAAA2600:9000:21f7:9e00:2:80be:5a80:93a1

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-1295.awsdns-33.org205.251.197.15
ns-1776.awsdns-30.co.uk205.251.198.240
ns-931.awsdns-52.net205.251.195.163
ns-105.awsdns-13.com205.251.192.105

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @smava.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
1aspmx.l.google.com142.250.110.26
5alt1.aspmx.l.google.com192.178.213.27
5alt2.aspmx.l.google.com142.251.127.27
10alt4.aspmx.l.google.com142.250.147.27
10alt3.aspmx.l.google.com172.253.148.27

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

NameContent
smava.deapple-domain-verification=DSLEC58tlBOYKoax
smava.degoogle-site-verification=nQ4cKwi6qeC8qxXgnWxgo0gRQtz4rYhN_UZjsJx3JuI
smava.denotion-domain-verification=VlbWWJZGHLxSse7C56HHfOZ1dSrMlHsYJvcUcbm1fmV
smava.deMS=ms70159517
smava.dev=spf1 include:spf0.smava.de ~all
smava.dedocusign=fe4aef43-97d4-4818-8407-89debb9e223c
smava.deonetrust-domain-verification=a2e1623f94894aef9a53381a2600a6a9
smava.deyahoo-verification-key=sSm5Va4KbLf55XFGdPhWOjrU+3c0hESG3JCXv8VI9hA=
smava.deR2CU2bQc=a3296287dab3bd3b6db8e355d4f95358
smava.deapple-domain-verification=CPZmu9JrDggijzlx
smava.deopenai-domain-verification=dv-8LIFlIEOOREJ0OlnJd4igFDz
smava.deanthropic-domain-verification-v1fm45=8McB1xnLWaZoR3ExmJhy3Rx4Q
smava.degoogle-site-verification=Gsn5-kJZAx8i7MxKuwxvLGU_gR6QH6uWaRUFQCQxKfI
smava.deatlassian-domain-verification=2DDCSFdX3KoR/ZVqjzWN00c2lgBDVMcFCpG5He5zN472azPfp3TvIa9zFP3nM6Bc
smava.desophos-domain-verification=cfe46ae1f6774e147c8e86444ad9179b916617b52f84ce48b281c5132d85beeb
smava.decloudflare_dashboard_sso=8ec6202acd5b8425a4eab4a64449df23
smava.defacebook-domain-verification=jqd676ero739mv9tszmyga4hin8sle
smava.demgverify=76d6ccc15feb5f0a381f72b10351f4ca53104558019308df36d1b2521638e538
_dmarc.smava.dev=DMARC1; p=quarantine; rua=mailto:[email protected]; sp=quarantine; pct=100
google._domainkey.smava.dev=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCPEIbMCe9v/Vj3xHU+y8SWqEAF/nb3kfrj/3GfiGqjcNJdkhQsMplatzMUTarE3YBEQlQzeAN54O9KZnl+IW5XPiDH4of5ImJAGTm339cfMNLmKYaaRhIuXdfC7nqF3ZyfQOAGH62JDyfZrs/lT5ZFsgwE6yYXZ4By769awNoERwIDAQAB
s1._domainkey.smava.dek=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAo/JWohUxdTSRcdbAr5/0UW1RgAMdJZpBs0x05MfXj5fRk2RvTSYZm0v1/LptIR1eelueHkoP6LaUxwki7F8IksZSzl55jK8HdSLDbHmpAMEIvz2TT4Fw3O1+Hyf2G2RewYYpApS1a7B6CmIwO0s42G3FSlRExMYgffOKiJz23ME/pP0Yv0lJUwKQuP2Fp89sTEysyFkoV2DWBMc4Mdd4kFAKllmloTn/Ym0hTrUt3ER3r6lRCKBwL3ynYvXHR5DkVMReSbAIcWBa7x5rGMN302CZJIp2FJMy/5LAyE3tyF3HwQKRKaWg5DFzcUrYL2LY5FjJLaRwjiq6Fq7A8MAvzQIDAQAB
s2._domainkey.smava.dek=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDF/2oDX3zb3/m4Sgledn9Cs8kyDK0ump4sMZHdPcJYaDszNbS9BbFZsVpq8eJzIAy08OwN5B8IUTwpoJH3oIxNMB8GhrQQy19wf9t/quxxD5nolo1kzY5qz8GfHk0wLYdsjs5kl9EPV8erBqrNQgwUqh87Tn8E2e8D0y/hQ//IaQIDAQAB
mailjet._domainkey.smava.dek=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDedtJDPQhPD+adJpFgW+h1nHc0+/oELptArk8GGMiXpIa35+4qjChGWDNtLe0Unj8TnukLtu+WT+JvYJyxRhm6LLVPX3wJvNN63LgszReU0lvpM10fN1cSs2GTaOw0hgnHBcUYw1uOZQELmnycbcD5qogxXUb3ZyS+6h6K53ku1wIDAQAB
zendesk1._domainkey.smava.dev=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.smava.dev=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
13.227.173.9Website13.227.173.0/24
13.227.173.112Website13.227.173.0/24
13.227.173.86Website13.227.173.0/24
13.227.173.121Website13.227.173.0/24
205.251.197.15Name server ns-1295.awsdns-33.org205.251.197.0/24
205.251.198.240Name server ns-1776.awsdns-30.co.uk205.251.198.0/24
205.251.195.163Name server ns-931.awsdns-52.net205.251.195.0/24
205.251.192.105Name server ns-105.awsdns-13.com205.251.192.0/24
142.250.110.26Mail server aspmx.l.google.com142.250.110.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com142.251.127.0/24
142.250.147.27Mail server alt4.aspmx.l.google.com142.250.147.0/24
172.253.148.27Mail server alt3.aspmx.l.google.com172.253.148.0/24

WHOIS of the domain smava.de

Domain: smava.de
Status: connect

% Query time: 353 msec
% WHEN: Fri Oct 02 23:24:23 UTC 2026