SPF Check: lotticards.de

Check SPF record for lotticards.de: ⊳Does a valid SPF record exist? ⊳What does it do? ⊳Which IPs are legitimate to send emails?

1. Specify domain name

Your data

Change specifications
Enter a domain to be checked for the SPF record
2. Specify IP address (optional)
Enter any IP address to check if it is authorized to send e-mails by the SPF record
Lookup for the domain:
lotticards.de
IP address to be checked:
no IP address specified
Loading...
Summary
An SPF record was found for the domain lotticards.de. The syntax check resulted in a total 7 error. The SPF record for lotticards.de is not valid. The e-mail spoofing protection for this domain is not or not sufficiently available. The SPF record contains a reference to external rules, which means that the validity of the SPF record depends on at least one other domain. A detailed list of the externally used "includes" can be found in the analysis result. In total 67 IP address(es) were authorized by the SPF record to send emails. 39 of which are not considered by the evaluation of the mail transfer agent and are not authorized to send emails on behalf of the domain. The SPF record analysis was performed on 13.06.2021 at 07:54:56 clock.

Let us check your SPF record or create a valid entry
Our experts will advise you at a fixed price including risk check for your domain. Avoid the risk of third parties misusing your domain. 30 days free reviews with functional guarantee.

Evaluation for the domain lotticards.de 

Nameserverset:
bonnie.ns.cloudflare.com
david.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
104.26.13.97 CLOUDFLARENET blacklist 
172.67.68.5 CLOUDFLARENET blacklist 
104.26.12.97 CLOUDFLARENET blacklist 
2606:4700:20:0:0:0:681a:c61 CLOUDFLARENET blacklist 
2606:4700:20:0:0:0:ac43:4405 CLOUDFLARENET blacklist 
2606:4700:20:0:0:0:681a:d61 CLOUDFLARENET blacklist 
66.102.1.27 GOOGLE blacklist 
2a00:1450:400c:c09:0:0:0:1a GOOGLE blacklist 
142.250.153.27 GOOGLE blacklist 
2a00:1450:4013:c16:0:0:0:1a GOOGLE blacklist 
142.251.9.27 GOOGLE blacklist 
2a00:1450:4025:c03:0:0:0:1a GOOGLE blacklist 
142.250.150.27 GOOGLE blacklist 
2a00:1450:4010:c1c:0:0:0:1a GOOGLE blacklist 
74.125.200.26 GOOGLE blacklist 
2404:6800:4003:c00:0:0:0:1b GOOGLE blacklist 
148.251.165.129 Hetzner Online GmbH blacklist 
35.190.247.0/24
GOOGLE blacklist 
64.233.160.0/19
GOOGLE blacklist 
66.102.0.0/20
GOOGLE blacklist 
66.249.80.0/20
GOOGLE blacklist 
72.14.192.0/18
GOOGLE blacklist 
74.125.0.0/16
GOOGLE blacklist 
108.177.8.0/21
GOOGLE blacklist 
173.194.0.0/16
GOOGLE blacklist 
209.85.128.0/17
GOOGLE blacklist 
216.58.192.0/19
GOOGLE blacklist 
216.239.32.0/19
GOOGLE blacklist 
2001:4860:4000::/36
GOOGLE blacklist 
2404:6800:4000::/36
GOOGLE blacklist 
2607:f8b0:4000::/36
GOOGLE blacklist 
2800:3f0:4000::/36
GOOGLE blacklist 
2a00:1450:4000::/36
GOOGLE blacklist 
2c0f:fb50:4000::/36
GOOGLE blacklist 
172.217.0.0/19
GOOGLE blacklist 
172.217.32.0/20
GOOGLE blacklist 
172.217.128.0/19
GOOGLE blacklist 
172.217.160.0/20
GOOGLE blacklist 
172.217.192.0/19
GOOGLE blacklist 
172.253.56.0/21
GOOGLE blacklist 
172.253.112.0/20
GOOGLE blacklist 
108.177.96.0/19
GOOGLE blacklist 
35.191.0.0/16
GOOGLE blacklist 
130.211.0.0/22
GOOGLE blacklist 
209.61.151.0/24
RMH-14 blacklist 
166.78.68.0/22
RACKSPACE blacklist 
198.61.254.0/23
RACKSPACE blacklist 
192.237.158.0/23
RACKSPACE blacklist 
23.253.182.0/23
RACKSPACE blacklist 
104.130.96.0/28
RACKSPACE blacklist 
146.20.113.0/24
RACKSPACE blacklist 
146.20.191.0/24
RACKSPACE blacklist 
159.135.224.0/20
RACKSPACE blacklist 
69.72.32.0/20
RACKSPACE blacklist 
104.130.122.0/23
RACKSPACE blacklist 
146.20.112.0/26
RACKSPACE blacklist 
141.193.32.0/23
AMAZON-02 blacklist 
161.38.192.0/20
AMAZON-AES blacklist 
143.55.224.0/20
MAILGUN blacklist 
141.193.32.0/23
AMAZON-02 blacklist 
159.135.140.80/29
Rackspace Ltd. blacklist 
159.135.132.128/25
Rackspace Ltd. blacklist 
161.38.204.0/22
AMAZON-02 blacklist 
87.253.232.0/21
Mailjet SAS blacklist 
185.189.236.0/22
Mailjet SAS blacklist 
185.211.120.0/22
Mailjet SAS blacklist 
185.250.236.0/22
Mailjet SAS blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: lotticards.de

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

104.26.13.97
172.67.68.5
104.26.12.97
2606:4700:20:0:0:0:681a:c61
2606:4700:20:0:0:0:ac43:4405
2606:4700:20:0:0:0:681a:d61

Additionally authorized A-records?

In addition to the A-records stored in the DNS, we were able to find further records authorized in the SPF-record

148.251.165.129

Are the registered mail servers allowed to send e-mails?

The mechanism 'mx' was set in the SPF entry. The following hosts are allowed to send

aspmx.l.google.com
aspmx.l.google.com
alt1.aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com
alt4.aspmx.l.google.com

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.google.com
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all
include:_netblocks.google.com
v=spf1 ip4:35.190.247.0/24 ip4:64.233.160.0/19 ip4:66.102.0.0/20 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:74.125.0.0/16 ip4:108.177.8.0/21 ip4:173.194.0.0/16 ip4:209.85.128.0/17 ip4:216.58.192.0/19 ip4:216.239.32.0/19 ~all
ipv4:
35.190.247.0/24
ipv4:
64.233.160.0/19
ipv4:
66.102.0.0/20
ipv4:
66.249.80.0/20
ipv4:
72.14.192.0/18
ipv4:
74.125.0.0/16
ipv4:
108.177.8.0/21
ipv4:
173.194.0.0/16
ipv4:
209.85.128.0/17
ipv4:
216.58.192.0/19
ipv4:
216.239.32.0/19
include:_netblocks2.google.com
v=spf1 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ~all
ipv6:
2001:4860:4000::/36
ipv6:
2404:6800:4000::/36
ipv6:
2607:f8b0:4000::/36
ipv6:
2800:3f0:4000::/36
ipv6:
2a00:1450:4000::/36
ipv6:
2c0f:fb50:4000::/36
include:_netblocks3.google.com
v=spf1 ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.253.56.0/21 ip4:172.253.112.0/20 ip4:108.177.96.0/19 ip4:35.191.0.0/16 ip4:130.211.0.0/22 ~all
ipv4:
172.217.0.0/19
ipv4:
172.217.32.0/20
ipv4:
172.217.128.0/19
ipv4:
172.217.160.0/20
ipv4:
172.217.192.0/19
ipv4:
172.253.56.0/21
ipv4:
172.253.112.0/20
ipv4:
108.177.96.0/19
ipv4:
35.191.0.0/16
ipv4:
130.211.0.0/22
include:mailgun.org
v=spf1 include:_spf.mailgun.org include:_spf.eu.mailgun.org -all
include:_spf.mailgun.org
v=spf1 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:141.193.32.0/23 ip4:161.38.192.0/20 ip4:143.55.224.0/20 ~all
ipv4:
209.61.151.0/24
ipv4:
166.78.68.0/22
ipv4:
198.61.254.0/23
ipv4:
192.237.158.0/23
ipv4:
23.253.182.0/23
ipv4:
104.130.96.0/28
ipv4:
146.20.113.0/24
ipv4:
146.20.191.0/24
ipv4:
159.135.224.0/20
ipv4:
69.72.32.0/20
ipv4:
104.130.122.0/23
ipv4:
146.20.112.0/26
ipv4:
141.193.32.0/23
ipv4:
161.38.192.0/20
ipv4:
143.55.224.0/20
include:_spf.eu.mailgun.org
v=spf1 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ~all
ipv4:
141.193.32.0/23
ipv4:
159.135.140.80/29
ipv4:
159.135.132.128/25
ipv4:
161.38.204.0/22
ipv4:
87.253.232.0/21
ipv4:
185.189.236.0/22
ipv4:
185.211.120.0/22
ipv4:
185.250.236.0/22

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

~all
SoftFail (non-compliant e-mails are accepted but marked)

Will be forwarded to another SPF record?

There is no reference to any other SPF record

Additionally authorized MX records

We could not find any other records authorized in the SPF record besides the MX records stored in the DNS

Additionally authorized IPv4 addresses

No explicit IPv4 addresses in the SPF record have been authorised to send

Additionally authorized IPv6 addresses

No explicit IPv6 addresses in the SPF record have been authorised to send

How is the sender informed?

The exp mechanism acts as a return to the sender if the IP address was not authorized to send and notify them. None was found.

PTR (obsolete mechanism)

The ptr mechanism is deprecated, slow and insecure and should not be used

PTR:

The ptr mechanism is deprecated, slow and insecure and should not be used

Authorize IP addresses with markers

When SPF is evaluated, macros can specifically authorize Ip addresses based on the request or connection of the user or client (RFC7208 )

Receiver address

analysis.ra-missing

Amount of reports

analysis.rp-missing

Report selection

analysis.rr-missing

Unknown mechanisms

No unknown mechanisms were found in the SPF record.

What is the SPF lookup for?

With the SPF lookup you analyze the SPF record of a domain for errors, security risks and authorized IP addresses. Optionally, you can specify an IP address to check if it is authorized to send e-mail on behalf of the domain. The SPF lookup analyzes registered TXT records in real time. If you want to specify an SPF record manually, use the SPF Analyzer.

How secure are your domains and where are the dangers lurking?

Domain risks are often underestimated

A current study by BITKOM reports on the alarming increase in cyber attacks on German companies, the ICANN warns of attacks on the global domain name system and the Federal Office for Information Security (BSI) sees significant risk potential in dealing with domain name. Unfortunately, these risks come into play every day, although this damage could have been prevented.

What should companies know and what can they do?

Practical and with many examples, the over 20-page eBook deals with the basics of domain risk management, specifies legal obligations and deals with responsibilities and liability issues. Numerous domain risks (e.g. "Domain Hijacking") are clearly described and the risk assessment and possible consequences are discussed.

Checklist: What about my own domain risks?

The Risk Atlas supports domain managers to get a first impression of their own risk potential in the company. The checklist includes 53 questions on 14 risk areas and enables a quick introduction to the topic.

⮩ Secure white paper "Domain Risk Management" for free

Server IP Address

We have determined the following IP address for the domain:

No domain specified

Reverse address

We have determined the following name for the server IP address:

104.26.13.97

© 2012 - 2021 nicmanager.com