SPF Check:
operalaboratori.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: 5 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain operalaboratori.com.
The SPF record for operalaboratori.com is not valid.
The syntax check resulted in a total of 5 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, 55 IP address(es) were authorized by the SPF record to send emails. 10 of these are not taken into account by the Mail Transfer Agent evaluation and are not authorized to send emails on behalf of the domain.

The SPF record analysis was performed on 12.10.2024 at 04:28:24 clock.

Lookup for the domain:
operalaboratori.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 operalaboratori.com 

Nameserverset:
dns3.arubadns.net
dns2.technorail.com
dns.technorail.com
dns4.arubadns.cz
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
46.28.0.49 Server Plan S.r.l. blacklist 
195.231.27.129 Aruba S.p.A. blacklist 
95.110.231.125 Aruba S.p.A. blacklist 
80.88.95.83 Aruba S.p.A. blacklist 
185.109.196.16 CTS Eventim Solutions GmbH blacklist 
185.47.61.203 Mythic Beasts Ltd blacklist 
185.47.61.62 Mythic Beasts Ltd blacklist 
81.2.196.113 INTERNET CZ, a.s. blacklist 
2001:15e8:102:1:0:0:0:c471 INTERNET CZ, a.s. blacklist 
81.2.193.0/24
INTERNET CZ, a.s. blacklist 
81.2.194.0/23
INTERNET CZ, a.s. blacklist 
81.2.196.0/24
INTERNET CZ, a.s. blacklist 
81.2.215.254/32
INTERNET CZ, a.s. blacklist 
64.99.180.0/26
TUCOWS blacklist 
185.129.138.0/23
INTERNET CZ, a.s. blacklist 
185.129.137.0/24
INTERNET CZ, a.s. blacklist 
194.182.79.97/32
INTERNET CZ, a.s. blacklist 
2001:15e8:102:1::c471 INTERNET CZ, a.s. blacklist 
62.149.128.0/24
Aruba S.p.A. blacklist 
62.149.158.0/24
Aruba S.p.A. blacklist 
62.149.157.0/24
Aruba S.p.A. blacklist 
62.149.176.0/22
Aruba S.p.A. blacklist 
62.149.156.0/24
Aruba S.p.A. blacklist 
62.149.155.0/24
Aruba S.p.A. blacklist 
62.149.152.0/24
Aruba S.p.A. blacklist 
62.149.188.0/22
Aruba S.p.A. blacklist 
95.110.216.0/22
Aruba S.p.A. blacklist 
94.177.209.0/24
Aruba S.p.A. blacklist 
185.196.164.0/24
Naquadria S.R.L. blacklist 
185.196.165.0/24
Naquadria S.R.L. blacklist 
88.99.25.169 Hetzner Online GmbH blacklist 
88.202.184.223 UK-2 Limited blacklist 
185.17.106.124 Keliweb S.R.L blacklist 
185.17.106.126 Keliweb S.R.L blacklist 
146.185.17.187 Hosting Services Inc blacklist 
146.185.17.85 Hosting Services Inc blacklist 
149.154.157.101 M247 Europe SRL blacklist 
2001:b60:1000:149:154:157:101:1 CDLAN SpA blacklist 
149.154.157.25 M247 Europe SRL blacklist 
178.63.44.156 Hetzner Online GmbH blacklist 
185.196.164.100 Naquadria S.R.L. blacklist 
185.196.164.101 Naquadria S.R.L. blacklist 
185.196.164.178 Naquadria S.R.L. blacklist 
185.196.164.0/24
Naquadria S.R.L. blacklist 
185.196.165.0/24
Naquadria S.R.L. blacklist 
83.149.178.26/29
Estracom SpA blacklist 
95.110.231.125 Aruba S.p.A. blacklist 
83.149.161.170/32
Estracom SpA blacklist 
195.231.27.129/32
Aruba S.p.A. blacklist 
95.110.231.123 Aruba S.p.A. blacklist 
95.110.231.124 Aruba S.p.A. blacklist 
95.110.231.125 Aruba S.p.A. blacklist 
95.110.231.126 Aruba S.p.A. blacklist 
95.110.231.127 Aruba S.p.A. blacklist 
95.110.231.128 Aruba S.p.A. blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: operalaboratori.com

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

46.28.0.49

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

185.109.196.16

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

esvacluster.security-mail.org
esvacloud.security-mail.org

Additionally authorized IPv4 addresses

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

80.88.95.83

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.opera.kloudymail.com
v=spf1 ip4:185.47.61.203 ip4:185.47.61.62 ~all
ipv4:
185.47.61.203
ipv4:
185.47.61.62
include:_spf.aruba.it
v=spf1 include:forpsi.com ip4:62.149.128.0/24 ip4:62.149.158.0/24 ip4:62.149.157.0/24 ip4:62.149.176.0/22 ip4:62.149.156.0/24 ip4:62.149.155.0/24 ip4:62.149.152.0/24 ip4:62.149.188.0/22 ip4:95.110.216.0/22 ip4:94.177.209.0/24 ?all
ipv4:
62.149.128.0/24
ipv4:
62.149.158.0/24
ipv4:
62.149.157.0/24
ipv4:
62.149.176.0/22
ipv4:
62.149.156.0/24
ipv4:
62.149.155.0/24
ipv4:
62.149.152.0/24
ipv4:
62.149.188.0/22
ipv4:
95.110.216.0/22
ipv4:
94.177.209.0/24
include:forpsi.com
v=spf1 mx ip4:81.2.193.0/24 ip4:81.2.194.0/23 ip4:81.2.196.0/24 ip4:81.2.215.254/32 ip4:64.99.180.0/26 ip4:185.129.138.0/23 ip4:185.129.137.0/24 ip4:194.182.79.97/32 ip6:2001:15e8:102:1::c471 -all
mx:
mx.forpsi.com
mx:
mx.forpsi.com
ipv4:
81.2.193.0/24
ipv4:
81.2.194.0/23
ipv4:
81.2.196.0/24
ipv4:
81.2.215.254/32
ipv4:
64.99.180.0/26
ipv4:
185.129.138.0/23
ipv4:
185.129.137.0/24
ipv4:
194.182.79.97/32
ipv6:
2001:15e8:102:1::c471
include:_spf.klsvc.net
v=spf1 ip4:185.196.164.0/24 ip4:185.196.165.0/24 ip4:88.99.25.169 ip4:88.202.184.223 ip4:185.17.106.124 ip4:185.17.106.126 ip4:146.185.17.187 ip4:146.185.17.85 include:_spf.mailer.sendings.email include:_spf.mailer.bubblesmail.net -all
ipv4:
185.196.164.0/24
ipv4:
185.196.165.0/24
ipv4:
88.99.25.169
ipv4:
88.202.184.223
ipv4:
185.17.106.124
ipv4:
185.17.106.126
ipv4:
146.185.17.187
ipv4:
146.185.17.85
include:_spf.mailer.sendings.email
v=spf1 ip4:149.154.157.101 ip6:2001:b60:1000:149:154:157:101:1 ip4:149.154.157.25 ip4:178.63.44.156 ~all
ipv4:
149.154.157.101
ipv4:
149.154.157.25
ipv4:
178.63.44.156
ipv6:
2001:b60:1000:149:154:157:101:1
include:_spf.mailer.bubblesmail.net
v=spf1 ip4:185.196.164.100 ip4:185.196.164.101 ip4:185.196.164.178 ip4:185.196.164.0/24 ip4:185.196.165.0/24 ~all
ipv4:
185.196.164.100
ipv4:
185.196.164.101
ipv4:
185.196.164.178
ipv4:
185.196.164.0/24
ipv4:
185.196.165.0/24
include:_spf.security-mail.org
v=spf1 ip4:83.149.178.26/29 a:esvacloud.security-mail.org include:_spf2.security-mail.org include:_spf3.security-mail.org -all
ipv4:
83.149.178.26/29
include:_spf2.security-mail.org
v=spf1 ip4:83.149.161.170/32 ip4:195.231.27.129/32 -all
ipv4:
83.149.161.170/32
ipv4:
195.231.27.129/32
include:_spf3.security-mail.org
v=spf1 ip4:95.110.231.123 ip4:95.110.231.124 ip4:95.110.231.125 ip4:95.110.231.126 ip4:95.110.231.127 ip4:95.110.231.128 -all
ipv4:
95.110.231.123
ipv4:
95.110.231.124
ipv4:
95.110.231.125
ipv4:
95.110.231.126
ipv4:
95.110.231.127
ipv4:
95.110.231.128

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

d01c85-tobugroup2.sphostserver.com

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