SPF Check:
transgourmet.de

1. Specify domain name

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

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.

Loading...

SPF check passed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 0 errors
  •   Email Anti-Spoofing: Good
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain transgourmet.de.
The SPF record for transgourmet.de is valid.
The syntax check of the SPF record shows no obvious errors.

Which IP-s are legitimate to send emails?
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 rules used externally can be found in the analysis result. In total, 66 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 18.11.2024 at 19:38:28 clock.

Lookup for the domain:
transgourmet.de
IP address to be checked:
no IP address specified
Solve your problems in no time
Guaranteed measurable improvement for email deliverability and domain security
Solve your problems in no time

Evaluation for the domain transgourmet.de 

Nameserverset:
ns1.coop.ch
ns1.ip-plus.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
52.101.68.15 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.68.10 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.68.12 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.73.1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
207.126.147.10 GOOGLE CLOUD NETWORKING blacklist 
207.126.147.12 GOOGLE CLOUD NETWORKING blacklist 
207.126.147.13 GOOGLE CLOUD NETWORKING blacklist 
207.126.147.14 GOOGLE CLOUD NETWORKING blacklist 
46.19.58.15 Mightycare Solutions GmbH blacklist 
46.19.58.30 Mightycare Solutions GmbH blacklist 
207.126.144.0/20
GOOGLE CLOUD NETWORKING blacklist 
193.200.253.78 Transgourmet Deutschland GmbH & Co. OHG blacklist 
23.253.32.145 RACKSPACE blacklist 
193.242.121.220 d.vinci HR-Systems GmbH blacklist 
193.242.121.221 d.vinci HR-Systems GmbH blacklist 
193.242.121.222 d.vinci HR-Systems GmbH blacklist 
82.98.120.115 Plus.line AG blacklist 
82.98.120.114 Plus.line AG blacklist 
62.50.112.106 LF.net Netzwerksysteme GmbH blacklist 
62.50.112.107 LF.net Netzwerksysteme GmbH blacklist 
62.50.112.110 LF.net Netzwerksysteme GmbH blacklist 
188.40.244.1 Hetzner Online GmbH blacklist 
88.99.64.201 Hetzner Online GmbH blacklist 
208.185.229.0/24
CYBERU blacklist 
208.185.235.0/24
ZAYO-6461 blacklist 
148.59.108.0/23
- blacklist 
148.59.106.0/23
- blacklist 
193.200.253.81 Transgourmet Deutschland GmbH & Co. OHG blacklist 
62.192.9.203 COLT Technology Services Group Limited blacklist 
62.192.9.204 COLT Technology Services Group Limited blacklist 
62.192.9.205 COLT Technology Services Group Limited blacklist 
77.73.242.11 IWB Industrielle Werke Basel blacklist 
77.73.242.12 IWB Industrielle Werke Basel blacklist 
77.73.242.13 IWB Industrielle Werke Basel blacklist 
194.11.164.43 Coop Genossenschaft blacklist 
194.11.164.44 Coop Genossenschaft blacklist 
194.11.164.41 Coop Genossenschaft blacklist 
194.11.164.42 Coop Genossenschaft blacklist 
104.130.70.5 RACKSPACE blacklist 
192.237.253.9 RACKSPACE blacklist 
23.253.174.11 RACKSPACE blacklist 
23.253.213.4 RACKSPACE blacklist 
23.253.213.7 RACKSPACE blacklist 
2001:4801:7822:103:be76:4eff:fe10:1260 RACKSPACE blacklist 
2001:4801:7824:104:be76:4eff:fe10:13e RACKSPACE blacklist 
2001:4801:7824:104:be76:4eff:fe10:7a2 RACKSPACE blacklist 
2001:4801:7825:104:be76:4eff:fe10:82 RACKSPACE blacklist 
2001:4801:7827:101:be76:4eff:fe10:978 RACKSPACE 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 
45.14.148.0/22
Mailjet SAS blacklist 
193.201.168.38/32
dpa Deutsche Presse-Agentur GmbH blacklist 
193.201.168.170/31
dpa Deutsche Presse-Agentur GmbH 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/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.102.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.103.0.0/17
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::/49
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:8000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:c000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:f000::/52
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: transgourmet.de

SPF record available?

We found an SPF record for the domain.

v=spf1

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

transgourmet-de.mail.protection.outlook.com
transgourmet-de.mail.protection.outlook.com
transgourmet-de.mail.protection.outlook.com
transgourmet-de.mail.protection.outlook.com

Additionally authorized IPv4 addresses

Explicit IPv4 addresses in the SPF record have been authorized to send

207.126.147.10
207.126.147.12
207.126.147.13
207.126.147.14
46.19.58.15
46.19.58.30
207.126.144.0/20
193.200.253.78
23.253.32.145
193.242.121.220
193.242.121.221
193.242.121.222
82.98.120.115
82.98.120.114
62.50.112.106
62.50.112.107
62.50.112.110
188.40.244.1
88.99.64.201
208.185.229.0/24
208.185.235.0/24
148.59.108.0/23
148.59.106.0/23
193.200.253.81
62.192.9.203
62.192.9.204
62.192.9.205
77.73.242.11
77.73.242.12
77.73.242.13
194.11.164.43
194.11.164.44
194.11.164.41
194.11.164.42

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.pantheon.io
v=spf1 ip4:104.130.70.5 ip4:192.237.253.9 ip4:23.253.174.11 ip4:23.253.213.4 ip4:23.253.213.7 ip6:2001:4801:7822:103:be76:4eff:fe10:1260 ip6:2001:4801:7824:104:be76:4eff:fe10:13e ip6:2001:4801:7824:104:be76:4eff:fe10:7a2 ip6:2001:4801:7825:104:be76:4eff:fe10:82 ip6:2001:4801:7827:101:be76:4eff:fe10:978 ~all
ipv4:
104.130.70.5
ipv4:
192.237.253.9
ipv4:
23.253.174.11
ipv4:
23.253.213.4
ipv4:
23.253.213.7
ipv6:
2001:4801:7822:103:be76:4eff:fe10:1260
ipv6:
2001:4801:7824:104:be76:4eff:fe10:13e
ipv6:
2001:4801:7824:104:be76:4eff:fe10:7a2
ipv6:
2001:4801:7825:104:be76:4eff:fe10:82
ipv6:
2001:4801:7827:101:be76:4eff:fe10:978
include:spf.mailjet.com
v=spf1 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:45.14.148.0/22 ~all
ipv4:
87.253.232.0/21
ipv4:
185.189.236.0/22
ipv4:
185.211.120.0/22
ipv4:
185.250.236.0/22
ipv4:
45.14.148.0/22
include:_spf.zimpel.de
v=spf1 ip4:193.201.168.38/32 ip4:193.201.168.170/31
ipv4:
193.201.168.38/32
ipv4:
193.201.168.170/31
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
52.100.0.0/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
ipv4:
104.47.0.0/17
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52

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.

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

Recently performed SPF lookups

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:

2620:12a:8001:0:0:0:0:2

Free whitepaper

How secure is your domain?

  • Practical with many examples
  • the basics of domain risk management summarized in 20 pages
  • Checklist with 53 questions on 14 risk areas

Get a first impression of the risk potential in your company

⮩ Download "Domain Risk Management" for free
All offers are aimed at traders, not end consumers and do not include VAT.
© 2024 nicmanager.com.   All rights reserved.
nicmanager