SPF Check:
galyff.fr

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

Does a valid SPF record exist?
An SPF record was found for the domain galyff.fr.
The SPF record for galyff.fr is not valid.
The syntax check resulted in a total of 2 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, 32 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 27.12.2024 at 04:41:46 clock.

Lookup for the domain:
galyff.fr
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 galyff.fr 

Nameserverset:
ks12.kalanda.net
ks4.kalanda.net
ks8.kalanda.net
ks16.kalanda.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
8.33.137.105/32
OVH SAS blacklist 
192.99.77.81/32
OVH SAS blacklist 
52.226.140.66 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.185.66.245 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.86.124.154 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.80.240.101/32
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
165.22.231.153/32
DIGITALOCEAN-ASN blacklist 
165.22.231.150/32
DIGITALOCEAN-ASN blacklist 
40.66.63.89/32
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.66.63.90/32
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.66.63.91/32
MICROSOFT-CORP-MSN-AS-BLOCK 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 
91.220.197.0/24
SAS Kalanda blacklist 
85.31.206.0/24
Free Pro SAS blacklist 
85.31.219.0/24
Free Pro SAS blacklist 
78.153.241.0/24
Free Pro SAS blacklist 
185.43.44.0/22
SAS Kalanda blacklist 
185.124.200.0/22
SAS Kalanda blacklist 
185.83.96.0/22
SAS Kalanda blacklist 
185.71.224.0/22
SAS Kalanda blacklist 
185.189.188.0/22
SAS Kalanda blacklist 
51.210.113.178 OVH SAS blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: galyff.fr

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

51.210.113.178

Additional external SPF records

We could find other records authorized in the SPF record

include:mx.ovh.com
v=spf1 ptr:mail-out.ovh.net ptr:mail.ovh.net ip4:8.33.137.105/32 ip4:192.99.77.81/32 ?all
ipv4:
8.33.137.105/32
ipv4:
192.99.77.81/32
include:spfcloud.letsignit.com
v=spf1 include:spf-us.letsignit.com include:spf-ca.letsignit.com ip4:40.66.63.89/32 ip4:40.66.63.90/32 ip4:40.66.63.91/32 ~all
ipv4:
40.66.63.89/32
ipv4:
40.66.63.90/32
ipv4:
40.66.63.91/32
include:spf-us.letsignit.com
v=spf1 ip4:52.226.140.66 ip4:52.185.66.245 ip4:13.86.124.154 ~all
ipv4:
52.226.140.66
ipv4:
52.185.66.245
ipv4:
13.86.124.154
include:spf-ca.letsignit.com
v=spf1 ip4:40.80.240.101/32 ip4:165.22.231.153/32 ip4:165.22.231.150/32 ~all
ipv4:
40.80.240.101/32
ipv4:
165.22.231.153/32
ipv4:
165.22.231.150/32
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:spf.kalanda.net
v=spf1 ip4:91.220.197.0/24 ip4:85.31.206.0/24 ip4:85.31.219.0/24 ip4:78.153.241.0/24 ip4:185.43.44.0/22 ip4:185.124.200.0/22 ip4:185.83.96.0/22 ip4:185.71.224.0/22 ip4:185.189.188.0/22 ~all
ipv4:
91.220.197.0/24
ipv4:
85.31.206.0/24
ipv4:
85.31.219.0/24
ipv4:
78.153.241.0/24
ipv4:
185.43.44.0/22
ipv4:
185.124.200.0/22
ipv4:
185.83.96.0/22
ipv4:
185.71.224.0/22
ipv4:
185.189.188.0/22

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:

ks185124200141.kalanda.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