SPF Check:
ciazumano.com

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 failed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 1 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain ciazumano.com.
The SPF record for ciazumano.com is not valid.
The syntax check resulted in a total of 1 errors.
of the email -Spoofing protection for this domain is not or not sufficiently provided.

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 26.11.2024 at 20:48:11 clock.

Lookup for the domain:
ciazumano.com
IP address to be checked:
no IP address specified

Have secure SPF record created by expert
from 749€

Order SPF record
  • 1. You send an email to our analysis system
  • 2. We will send you the finished SPF record
  • 3. You implement the SPF record
  • 4. We check the setup final
Have secure SPF record created by expert
from 749€

Evaluation for the domain ciazumano.com 

Nameserverset:
pdns07.domaincontrol.com
pdns08.domaincontrol.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
216.46.17.160/27
OPENFACE blacklist 
216.46.18.64/27
OPENFACE blacklist 
12.129.35.0/27
ATT-INTERNET4 blacklist 
66.244.67.0/27
CORNERSTONE 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 
204.232.250.0/24
RACKSPACE blacklist 
5.152.185.0/24
Zix International AG blacklist 
8.19.118.0/24
ASN-CUST blacklist 
8.31.233.0/24
AS-APPRIVER blacklist 
72.3.212.195 RMH-14 blacklist 
5.152.188.0/24
Zix International AG blacklist 
174.37.170.192/27
SOFTLAYER blacklist 
75.126.84.128/26
SOFTLAYER blacklist 
67.228.8.0/25
SOFTLAYER blacklist 
67.227.149.19 LIQUIDWEB blacklist 
64.56.208.32/27
GREENVIEWDATA blacklist 
67.228.91.90 SOFTLAYER blacklist 
67.228.158.174 SOFTLAYER blacklist 
174.36.44.116/30
SOFTLAYER blacklist 
50.201.66.168 GREENVIEWDATA blacklist 
63.71.8.0/21
ASN-CUST blacklist 
199.30.232.0/21
ASN-CUST blacklist 
74.203.184.0/23
AS-APPRIVER blacklist 
207.195.176.0/20
ASN-CUST 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 
54.213.101.86 AMAZON-02 blacklist 
54.213.101.90 AMAZON-02 blacklist 
54.200.5.133 AMAZON-02 blacklist 
54.218.238.220 AMAZON-02 blacklist 
54.187.103.206 AMAZON-02 blacklist 
54.200.182.110 AMAZON-02 blacklist 
52.40.203.205 AMAZON-02 blacklist 
52.89.177.132 AMAZON-02 blacklist 
52.39.127.104 AMAZON-02 blacklist 
34.223.183.171 AMAZON-02 blacklist 
54.185.198.195 AMAZON-02 blacklist 
54.185.51.55 AMAZON-02 blacklist 
54.214.75.131 AMAZON-02 blacklist 
103.151.192.0/23
AMAZON-02 blacklist 
185.12.80.0/22
- blacklist 
188.172.128.0/20
- blacklist 
192.161.144.0/20
- blacklist 
216.198.0.0/18
AMAZON-02 blacklist 
63.131.146.17 DATAPIPE-SEA blacklist 
169.145.39.240/29
SAP-DC-NS blacklist 
12.129.35.0/27
ATT-INTERNET4 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: ciazumano.com

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

216.46.17.160/27
216.46.18.64/27
12.129.35.0/27
66.244.67.0/27
63.131.146.17

Additional external SPF records

We could find other records authorized in the SPF record

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:edgepilot.com
v=spf1 include:spf1.appriver.com include:spf2.appriver.com include:spf.protection.outlook.com ~all
include:spf1.appriver.com
v=spf1 ip4:204.232.250.0/24 ip4:5.152.185.0/24 ip4:8.19.118.0/24 ip4:8.31.233.0/24 ip4:72.3.212.195 ip4:5.152.188.0/24 ip4:174.37.170.192/27 ~all
ipv4:
204.232.250.0/24
ipv4:
5.152.185.0/24
ipv4:
8.19.118.0/24
ipv4:
8.31.233.0/24
ipv4:
72.3.212.195
ipv4:
5.152.188.0/24
ipv4:
174.37.170.192/27
include:spf2.appriver.com
v=spf1 ip4:75.126.84.128/26 ip4:67.228.8.0/25 ip4:67.227.149.19 ip4:64.56.208.32/27 ip4:67.228.91.90 ip4:67.228.158.174 ip4:174.36.44.116/30 ip4:50.201.66.168 ip4:63.71.8.0/21 ip4:199.30.232.0/21 ip4:74.203.184.0/23 ip4:207.195.176.0/20 ~all
ipv4:
75.126.84.128/26
ipv4:
67.228.8.0/25
ipv4:
67.227.149.19
ipv4:
64.56.208.32/27
ipv4:
67.228.91.90
ipv4:
67.228.158.174
ipv4:
174.36.44.116/30
ipv4:
50.201.66.168
ipv4:
63.71.8.0/21
ipv4:
199.30.232.0/21
ipv4:
74.203.184.0/23
ipv4:
207.195.176.0/20
include:spf.protection.outlook.com (Domain has already been resolved once)
include:spf.happyfox.com
v=spf1 ip4:54.213.101.86 ip4:54.213.101.90 ip4:54.200.5.133 ip4:54.218.238.220 ip4:54.187.103.206 ip4:54.200.182.110 ip4:52.40.203.205 ip4:52.89.177.132 ip4:52.39.127.104 ip4:34.223.183.171 ip4:54.185.198.195 ip4:54.185.51.55 ip4:54.214.75.131 ~all
ipv4:
54.213.101.86
ipv4:
54.213.101.90
ipv4:
54.200.5.133
ipv4:
54.218.238.220
ipv4:
54.187.103.206
ipv4:
54.200.182.110
ipv4:
52.40.203.205
ipv4:
52.89.177.132
ipv4:
52.39.127.104
ipv4:
34.223.183.171
ipv4:
54.185.198.195
ipv4:
54.185.51.55
ipv4:
54.214.75.131
include:mail.zendesk.com
v=spf1 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ~all
ipv4:
103.151.192.0/23
ipv4:
185.12.80.0/22
ipv4:
188.172.128.0/20
ipv4:
192.161.144.0/20
ipv4:
216.198.0.0/18
include:_spf.concurcompleat.com
v=spf1 ip4:169.145.39.240/29 ip4:12.129.35.0/27 ~all
ipv4:
169.145.39.240/29
ipv4:
12.129.35.0/27

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:

198.185.159.145

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