SPF Check:
engadin.cloud

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
Warning: Compliance breach for email deliverability & security

The domain engadin.cloud does not fulfil the requirements for optimal deliverability to Google, Yahoo and other email service providers.

Mandatory IT baseline protection measures for email security are not fulfilled. There are risks of email misuse.

Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain engadin.cloud.
The SPF record for engadin.cloud 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, 50 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 19.04.2024 at 17:29:38 clock.

Lookup for the domain:
engadin.cloud
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 engadin.cloud 

Nameserverset:
ch.pro.io
p.dnh.net
nl.pro.io
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
212.11.79.0/24
GOOGLE-CLOUD-PLATFORM 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::/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 
77.74.4.144 Abacus Research AG blacklist 
46.227.224.147 Abacus Research AG blacklist 
2a02:cd8:abac:27::13 Abacus Research AG blacklist 
46.227.226.102 Abacus Research AG blacklist 
46.227.226.108 Abacus Research AG blacklist 
46.227.226.21 Abacus Research AG blacklist 
46.227.228.154 Abacus Research AG blacklist 
46.227.228.228 Abacus Research AG blacklist 
46.227.228.28 Abacus Research AG blacklist 
2a02:cd8:2ee3:e200::15 Abacus Research AG blacklist 
2a02:cd8:2ee3:e200::65 Abacus Research AG blacklist 
2a02:cd8:2ee3:e200::7b Abacus Research AG blacklist 
2a02:cd8:2ee3:e400::1c Abacus Research AG blacklist 
2a02:cd8:2ee3:e400::293 Abacus Research AG blacklist 
2a02:cd8:2ee3:e400::446 Abacus Research AG blacklist 
104.40.229.156 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.169.0.179 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
191.237.4.149 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.209.35.28 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.210.80.79 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.70.157.244 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.140.37.132 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.141.5.228 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.172.222.27 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.172.38.8 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.233.37.155 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.242.32.10 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.233.10.24 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.74.156.16 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.52.124.58 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.113.192.118 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.40.229.156 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.169.0.179 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.50.220.144/28
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.127.253.48/28
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
77.74.4.142 Abacus Research AG blacklist 
185.243.67.1/29
connecta ag blacklist 
185.106.133.0/24
i-Community AG blacklist 
2a10:1380::/29
i-Community AG blacklist 
217.196.79.132 Jumper GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: engadin.cloud

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized IPv4 addresses

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

217.196.79.132

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.mailersend.net
v=spf1 ip4:212.11.79.0/24 ~all
ipv4:
212.11.79.0/24
include:spf.engadin.cloud
v=spf1 include:spf.protection.outlook.com include:spf.abacuscity.ch include:spf.exclaimer.net include:spf.eu.exclaimer.net ip4:77.74.4.142 ip4:185.243.67.1/29 ip4:185.106.133.0/24 ip6:2a10:1380::/29 -all
ipv4:
77.74.4.142
ipv4:
185.243.67.1/29
ipv4:
185.106.133.0/24
ipv6:
2a10:1380::/29
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::/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/14
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:spf.abacuscity.ch
v=spf1 ip4:77.74.4.144 ip4:46.227.224.147 ip6:2a02:cd8:abac:27::13 ip4:46.227.226.102 ip4:46.227.226.108 ip4:46.227.226.21 ip4:46.227.228.154 ip4:46.227.228.228 ip4:46.227.228.28 ip6:2a02:cd8:2ee3:e200::15 ip6:2a02:cd8:2ee3:e200::65 ip6:2a02:cd8:2ee3:e200::7b ip6:2a02:cd8:2ee3:e400::1c ip6:2a02:cd8:2ee3:e400::293 ip6:2a02:cd8:2ee3:e400::446 -all
ipv4:
77.74.4.144
ipv4:
46.227.224.147
ipv4:
46.227.226.102
ipv4:
46.227.226.108
ipv4:
46.227.226.21
ipv4:
46.227.228.154
ipv4:
46.227.228.228
ipv4:
46.227.228.28
ipv6:
2a02:cd8:abac:27::13
ipv6:
2a02:cd8:2ee3:e200::15
ipv6:
2a02:cd8:2ee3:e200::65
ipv6:
2a02:cd8:2ee3:e200::7b
ipv6:
2a02:cd8:2ee3:e400::1c
ipv6:
2a02:cd8:2ee3:e400::293
ipv6:
2a02:cd8:2ee3:e400::446
include:spf.exclaimer.net
v=spf1 ip4:104.40.229.156 ip4:52.169.0.179 ip4:191.237.4.149 ip4:104.209.35.28 ip4:104.210.80.79 ip4:13.70.157.244 ip4:51.140.37.132 ip4:51.141.5.228 ip4:52.172.222.27 ip4:52.172.38.8 ip4:52.233.37.155 ip4:52.242.32.10 ip4:20.233.10.24 ip4:20.74.156.16 ip4:20.52.124.58 ip4:20.113.192.118 ~all
ipv4:
104.40.229.156
ipv4:
52.169.0.179
ipv4:
191.237.4.149
ipv4:
104.209.35.28
ipv4:
104.210.80.79
ipv4:
13.70.157.244
ipv4:
51.140.37.132
ipv4:
51.141.5.228
ipv4:
52.172.222.27
ipv4:
52.172.38.8
ipv4:
52.233.37.155
ipv4:
52.242.32.10
ipv4:
20.233.10.24
ipv4:
20.74.156.16
ipv4:
20.52.124.58
ipv4:
20.113.192.118
include:spf.eu.exclaimer.net
v=spf1 ip4:104.40.229.156 ip4:52.169.0.179 ip4:20.50.220.144/28 ip4:40.127.253.48/28 ~all
ipv4:
104.40.229.156
ipv4:
52.169.0.179
ipv4:
20.50.220.144/28
ipv4:
40.127.253.48/28

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

tesla.sui-inter.net

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   Connected by Team Internet