SPF Check:
datasec.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 datasec.de.
The SPF record for datasec.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, 41 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 16.11.2024 at 11:48:26 clock.

Lookup for the domain:
datasec.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 datasec.de 

Nameserverset:
ns1.easyname.eu
ns2.easyname.eu
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
91.194.222.1 Vodafone GmbH blacklist 
88.79.217.5 Vodafone GmbH blacklist 
91.194.222.5 Vodafone GmbH blacklist 
212.83.34.192 23M GmbH blacklist 
91.194.222.199 Vodafone GmbH blacklist 
91.194.222.5 Vodafone GmbH blacklist 
88.79.217.5 Vodafone GmbH blacklist 
91.194.222.1 Vodafone 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 
23.253.182.103 RACKSPACE blacklist 
23.253.183.145 RACKSPACE blacklist 
23.253.183.146 RACKSPACE blacklist 
23.253.183.147 RACKSPACE blacklist 
23.253.183.148 RACKSPACE blacklist 
23.253.183.150 RACKSPACE blacklist 
166.78.68.221 RACKSPACE blacklist 
167.89.46.159 SENDGRID blacklist 
167.89.64.9 SENDGRID blacklist 
167.89.65.0 SENDGRID blacklist 
167.89.65.53 SENDGRID blacklist 
167.89.65.100 SENDGRID blacklist 
167.89.74.233 SENDGRID blacklist 
167.89.75.33 SENDGRID blacklist 
167.89.75.126 SENDGRID blacklist 
167.89.75.136 SENDGRID blacklist 
167.89.75.164 SENDGRID blacklist 
192.237.159.42 RACKSPACE blacklist 
192.237.159.43 RACKSPACE blacklist 
159.112.242.162 MAILGUN blacklist 
159.135.228.10 MAILGUN blacklist 
91.151.16.72 Nessus GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: datasec.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

212.83.34.192

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

91.151.16.72

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

sec-gw.datasec.de
sec-mail.datasec.de
sec-mail.datasec.de

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.datasec.de
v=spf1 ip4:91.194.222.199 ip4:91.194.222.5 ip4:88.79.217.5 ip4:91.194.222.1 -all
ipv4:
91.194.222.199
ipv4:
91.194.222.5
ipv4:
88.79.217.5
ipv4:
91.194.222.1
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
include:stspg-customer.com
v=spf1 ip4:23.253.182.103 ip4:23.253.183.145 ip4:23.253.183.146 ip4:23.253.183.147 ip4:23.253.183.148 ip4:23.253.183.150 ip4:166.78.68.221 ip4:167.89.46.159 ip4:167.89.64.9 ip4:167.89.65.0 ip4:167.89.65.53 ip4:167.89.65.100 ip4:167.89.74.233 ip4:167.89.75.33 ip4:167.89.75.126 ip4:167.89.75.136 ip4:167.89.75.164 ip4:192.237.159.42 ip4:192.237.159.43 ip4:159.112.242.162 ip4:159.135.228.10 -all
ipv4:
23.253.182.103
ipv4:
23.253.183.145
ipv4:
23.253.183.146
ipv4:
23.253.183.147
ipv4:
23.253.183.148
ipv4:
23.253.183.150
ipv4:
166.78.68.221
ipv4:
167.89.46.159
ipv4:
167.89.64.9
ipv4:
167.89.65.0
ipv4:
167.89.65.53
ipv4:
167.89.65.100
ipv4:
167.89.74.233
ipv4:
167.89.75.33
ipv4:
167.89.75.126
ipv4:
167.89.75.136
ipv4:
167.89.75.164
ipv4:
192.237.159.42
ipv4:
192.237.159.43
ipv4:
159.112.242.162
ipv4:
159.135.228.10

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

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.

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:

ms40.flipzoom.de

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