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.
IP | Provider / ASN | DNSBL-Check | ||
---|---|---|---|---|
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 |
(spaenex.info → spf.protection.outlook.com → spfd.protection.outlook.com) Mechanisms are separated by exactly one space.
spfd.protection.outlook.com -> Mechanisms are separated by exactly one space.
|
(spaenex.info → spf.protection.outlook.com → spfd.protection.outlook.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '51.4.72.0/24'
OK for 'ip4' -> '51.5.72.0/24'
OK for 'ip4' -> '51.5.80.0/27'
OK for 'ip4' -> '20.47.149.138/32'
OK for 'ip4' -> '51.4.80.0/27'
OK for 'ip6' -> '2a01:4180:4051:0800::/64'
OK for 'ip6' -> '2a01:4180:4050:0800::/64'
OK for 'ip6' -> '2a01:4180:4051:0400::/64'
OK for 'ip6' -> '2a01:4180:4050:0400::/64'
OK for 'all' -> '-'
|
(spaenex.info → spf.protection.outlook.com → spfd.protection.outlook.com) The SPF consists of a permissible character set.
The SPF record of spfd.protection.outlook.com contains valid characters.
|
(spaenex.info → spf.protection.outlook.com) Mechanisms are separated by exactly one space.
spf.protection.outlook.com -> Mechanisms are separated by exactly one space.
|
(spaenex.info → spf.protection.outlook.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '40.92.0.0/15'
OK for 'ip4' -> '40.107.0.0/16'
OK for 'ip4' -> '52.100.0.0/14'
OK for 'ip4' -> '104.47.0.0/17'
OK for 'ip6' -> '2a01:111:f400::/48'
OK for 'ip6' -> '2a01:111:f403::/48'
OK for 'include' -> 'spfd.protection.outlook.com'
OK for 'all' -> '-'
|
(spaenex.info → spf.protection.outlook.com) The SPF consists of a permissible character set.
The SPF record of spf.protection.outlook.com contains valid characters.
|
(spaenex.info) Mechanisms are separated by exactly one space.
spaenex.info -> Mechanisms are separated by exactly one space.
|
(spaenex.info) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'include' -> 'spf.protection.outlook.com'
OK for 'all' -> '-'
|
(spaenex.info) The DNS lookup limit was not exceeded.
The limit was not exceeded:
1: spaenex.info include:spf.protection.outlook.com 2: spaenex.info include:spf.protection.outlook.com include:spfd.protection.outlook.com |
(spaenex.info) The SPF consists of a permissible character set.
The SPF record of spaenex.info contains valid characters.
|
SPF record available?
We found an SPF record for the domain.
Additional external SPF records
We could find other records authorized in the SPF record
E-Mail handling
How should the checkHost() function of the e-mail server handle the e-mail? (syntax )
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 )
Unknown mechanisms
No unknown mechanisms were found in the SPF record.
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.
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.
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:
w06.rzone.de