SPF Check: infrest.de

Check SPF record for infrest.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:
infrest.de
IP address to be checked:
no IP address specified
Loading...
Summary
An SPF record was found for the domain infrest.de. The syntax check of the SPF record does not show any obvious errors. The SPF record for infrest.de is valid. 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 43 IP address(es) were authorized by the SPF record to send emails. The SPF record analysis was performed on 27.07.2021 at 14:47:08 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 infrest.de 

Nameserverset:
ns1-08.azure-dns.com
ns2-08.azure-dns.net
ns3-08.azure-dns.org
ns4-08.azure-dns.info
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
141.16.94.244 - blacklist 
141.16.94.245 - blacklist 
213.23.82.72 Vodafone GmbH blacklist 
62.112.136.233 Zurich Datacenter Ag blacklist 
62.112.136.234 Zurich Datacenter Ag blacklist 
62.112.137.244 Zurich Datacenter Ag blacklist 
62.112.137.245 Zurich Datacenter Ag blacklist 
62.112.137.247 Zurich Datacenter Ag blacklist 
62.112.137.251 Zurich Datacenter Ag blacklist 
80.148.33.47 Deutsche Telekom AG blacklist 
195.36.120.51 Computacenter AG & Co.oHG blacklist 
217.33.119.92 British Telecommunications PLC blacklist 
217.33.119.93 British Telecommunications PLC blacklist 
195.36.75.150 Computacenter AG & Co.oHG blacklist 
195.36.75.151 Computacenter AG & Co.oHG blacklist 
188.95.96.121 Telecitygroup International Limited blacklist 
155.56.221.13 SAP SE blacklist 
155.56.221.14 SAP SE blacklist 
40.92.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.107.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.100.0.0/14
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.47.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f400::/48
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403::/48
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.4.72.0/24
Microsoft Deutschland MCIO GmbH blacklist 
51.5.72.0/24
Microsoft Deutschland MCIO GmbH blacklist 
51.5.80.0/27
Microsoft Deutschland MCIO GmbH blacklist 
20.47.149.138/32
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.4.80.0/27
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4051:0800::/64
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4050:0800::/64
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4051:0400::/64
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4050:0400::/64
Microsoft Deutschland MCIO GmbH blacklist 
185.41.28.0/22
Sendinblue SAS blacklist 
94.143.16.0/21
Sendinblue SAS blacklist 
185.24.144.0/22
Sendinblue SAS blacklist 
153.92.224.0/19
Sendinblue SAS blacklist 
213.32.128.0/18
Sendinblue SAS blacklist 
185.107.232.0/22
Sendinblue SAS blacklist 
77.32.128.0/18
Sendinblue SAS blacklist 
77.32.192.0/19
Sendinblue SAS blacklist 
212.146.192.0/18
Sendinblue SAS blacklist 
172.246.0.0/18
Sendinblue SAS blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: infrest.de

SPF record available?

We found an SPF record for the domain.

v=spf1

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf2.gasag.de
v=spf1 ip4:141.16.94.244 ip4:141.16.94.245 ip4:213.23.82.72 ip4:62.112.136.233 ip4:62.112.136.234 ip4:62.112.137.244 ip4:62.112.137.245 ip4:62.112.137.247 ip4:62.112.137.251 ip4:80.148.33.47 ~all
ipv4:
141.16.94.244
ipv4:
141.16.94.245
ipv4:
213.23.82.72
ipv4:
62.112.136.233
ipv4:
62.112.136.234
ipv4:
62.112.137.244
ipv4:
62.112.137.245
ipv4:
62.112.137.247
ipv4:
62.112.137.251
ipv4:
80.148.33.47
include:_spf3.gasag.de
v=spf1 ip4:195.36.120.51 ~all
ipv4:
195.36.120.51
include:_spf4.gasag.de
v=spf1 ip4:217.33.119.92 ip4:217.33.119.93 ip4:195.36.75.150 ip4:195.36.75.151 ip4:188.95.96.121 ip4:155.56.221.13 ip4:155.56.221.14 ~all
ipv4:
217.33.119.92
ipv4:
217.33.119.93
ipv4:
195.36.75.150
ipv4:
195.36.75.151
ipv4:
188.95.96.121
ipv4:
155.56.221.13
ipv4:
155.56.221.14
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/14 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/48 include:spfd.protection.outlook.com -all
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
52.100.0.0/14
ipv4:
104.47.0.0/17
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/48
include:spfd.protection.outlook.com
v=spf1 ip4:51.4.72.0/24 ip4:51.5.72.0/24 ip4:51.5.80.0/27 ip4:20.47.149.138/32 ip4:51.4.80.0/27 ip6:2a01:4180:4051:0800::/64 ip6:2a01:4180:4050:0800::/64 ip6:2a01:4180:4051:0400::/64 ip6:2a01:4180:4050:0400::/64 -all
ipv4:
51.4.72.0/24
ipv4:
51.5.72.0/24
ipv4:
51.5.80.0/27
ipv4:
20.47.149.138/32
ipv4:
51.4.80.0/27
ipv6:
2a01:4180:4051:0800::/64
ipv6:
2a01:4180:4050:0800::/64
ipv6:
2a01:4180:4051:0400::/64
ipv6:
2a01:4180:4050:0400::/64
include:spf.sendinblue.com
v=spf1 ip4:185.41.28.0/22 ip4:94.143.16.0/21 ip4:185.24.144.0/22 ip4:153.92.224.0/19 ip4:213.32.128.0/18 ip4:185.107.232.0/22 ip4:77.32.128.0/18 ip4:77.32.192.0/19 ip4:212.146.192.0/18 ip4:172.246.0.0/18 ~all
ipv4:
185.41.28.0/22
ipv4:
94.143.16.0/21
ipv4:
185.24.144.0/22
ipv4:
153.92.224.0/19
ipv4:
213.32.128.0/18
ipv4:
185.107.232.0/22
ipv4:
77.32.128.0/18
ipv4:
77.32.192.0/19
ipv4:
212.146.192.0/18
ipv4:
172.246.0.0/18

E-Mail handling

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

-all
Fail (non-compliant e-mails are rejected)

Will be forwarded to another SPF record?

There is no reference to any other SPF record

Are the server addresses allowed to send e-mails?

In the SPF entry the mechanism 'a' has not been set.

Additionally authorized A-records?

In addition to the A-Records stored in the DNS, we could not find any other records authorized in the SPF-Record.

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

In the SPF entry the mechanism 'mx' has not been set

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:

gasag-itacs

© 2012 - 2021 nicmanager.com