SPF Check:
serviciomigraciones.cl

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

The domain serviciomigraciones.cl 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 serviciomigraciones.cl.
The SPF record for serviciomigraciones.cl 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, 71 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 02.05.2024 at 04:53:57 clock.

Lookup for the domain:
serviciomigraciones.cl
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 serviciomigraciones.cl 

Nameserverset:
nelci.ns.cloudflare.com
jaime.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
172.67.144.67 CLOUDFLARENET blacklist 
104.21.28.53 - CLOUDFLARENET blacklist 
2606:4700:3033:0:0:0:ac43:9043 CLOUDFLARENET blacklist 
2606:4700:3031:0:0:0:6815:1c35 CLOUDFLARENET blacklist 
142.251.168.26 GOOGLE blacklist 
2a00:1450:400c:c0c:0:0:0:1b GOOGLE blacklist 
142.250.150.26 GOOGLE blacklist 
2a00:1450:4010:c1c:0:0:0:1b GOOGLE blacklist 
74.125.200.27 GOOGLE blacklist 
2404:6800:4003:c00:0:0:0:1b GOOGLE blacklist 
142.250.153.27 GOOGLE blacklist 
2a00:1450:4013:c16:0:0:0:1a GOOGLE blacklist 
142.251.9.27 GOOGLE blacklist 
2a00:1450:4025:c03:0:0:0:1a GOOGLE blacklist 
35.190.247.0/24
GOOGLE-CLOUD-PLATFORM blacklist 
64.233.160.0/19
GOOGLE blacklist 
66.102.0.0/20
GOOGLE blacklist 
66.249.80.0/20
GOOGLE blacklist 
72.14.192.0/18
GOOGLE blacklist 
74.125.0.0/16
GOOGLE blacklist 
108.177.8.0/21
GOOGLE blacklist 
173.194.0.0/16
GOOGLE blacklist 
209.85.128.0/17
GOOGLE blacklist 
216.58.192.0/19
GOOGLE blacklist 
216.239.32.0/19
GOOGLE blacklist 
2001:4860:4000::/36
GOOGLE blacklist 
2404:6800:4000::/36
GOOGLE blacklist 
2607:f8b0:4000::/36
GOOGLE blacklist 
2800:3f0:4000::/36
GOOGLE blacklist 
2a00:1450:4000::/36
GOOGLE blacklist 
2c0f:fb50:4000::/36
GOOGLE blacklist 
172.217.0.0/19
GOOGLE blacklist 
172.217.32.0/20
GOOGLE blacklist 
172.217.128.0/19
GOOGLE blacklist 
172.217.160.0/20
GOOGLE blacklist 
172.217.192.0/19
GOOGLE blacklist 
172.253.56.0/21
GOOGLE blacklist 
172.253.112.0/20
GOOGLE blacklist 
108.177.96.0/19
GOOGLE blacklist 
35.191.0.0/16
GOOGLE blacklist 
130.211.0.0/22
GOOGLE-CLOUD-PLATFORM blacklist 
200.75.30.33/27
Gtd Internet S.A. blacklist 
2604:a880:4:1d0::119:8000 DIGITALOCEAN-ASN blacklist 
190.215.200.120/29
Gtd Internet S.A. blacklist 
186.79.108.139 TELEFONICA CHILE S.A. blacklist 
45.33.11.242 Akamai Connected Cloud blacklist 
170.150.142.3 Gtd Internet S.A. blacklist 
173.255.195.198 Akamai Connected Cloud blacklist 
172.234.18.96 Akamai Connected Cloud blacklist 
172.232.171.4 Akamai Connected Cloud blacklist 
172.233.234.73 Akamai Connected Cloud blacklist 
173.255.195.198 Akamai Connected Cloud blacklist 
104.237.134.98 Akamai Connected Cloud blacklist 
172.233.142.227 Akamai Connected Cloud blacklist 
69.164.213.18 Akamai Connected Cloud blacklist 
172.232.171.179 Akamai Connected Cloud blacklist 
172.233.224.71 Akamai Connected Cloud blacklist 
45.56.69.127 Akamai Connected Cloud blacklist 
172.232.172.209 Akamai Connected Cloud blacklist 
165.232.142.117 DIGITALOCEAN-ASN blacklist 
2600:3c00::f03c:93ff:fee4:acb8 Akamai Connected Cloud blacklist 
2600:3c0a::f03c:93ff:fee4:92af Akamai Connected Cloud blacklist 
2600:3c00::f03c:93ff:fee4:94a5 Akamai Connected Cloud blacklist 
2600:3c00::f03c:93ff:fee1:0521 Akamai Connected Cloud blacklist 
2600:3c06::f03c:93ff:fe6e:c0b1 Akamai Connected Cloud blacklist 
2600:3c0a::f03c:93ff:fe6e:4d94 Akamai Connected Cloud blacklist 
2600:3c05::f03c:93ff:fe73:fca6 Akamai Connected Cloud blacklist 
2a01:7e03::f03c:93ff:fee4:2b41 Akamai Connected Cloud blacklist 
2600:3c03::f03c:93ff:fee4:1739 Akamai Connected Cloud blacklist 
2600:3c0a::f03c:93ff:fee4:2b0c Akamai Connected Cloud blacklist 
2600:3c05::f03c:94ff:fe7a:8190 Akamai Connected Cloud blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: serviciomigraciones.cl

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

172.67.144.67
104.21.28.53
2606:4700:3033:0:0:0:ac43:9043
2606:4700:3031:0:0:0:6815:1c35

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

aspmx.l.google.com
aspmx.l.google.com
alt3.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com
alt4.aspmx.l.google.com
alt1.aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt2.aspmx.l.google.com

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.google.com
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all
include:_netblocks.google.com
v=spf1 ip4:35.190.247.0/24 ip4:64.233.160.0/19 ip4:66.102.0.0/20 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:74.125.0.0/16 ip4:108.177.8.0/21 ip4:173.194.0.0/16 ip4:209.85.128.0/17 ip4:216.58.192.0/19 ip4:216.239.32.0/19 ~all
ipv4:
35.190.247.0/24
ipv4:
64.233.160.0/19
ipv4:
66.102.0.0/20
ipv4:
66.249.80.0/20
ipv4:
72.14.192.0/18
ipv4:
74.125.0.0/16
ipv4:
108.177.8.0/21
ipv4:
173.194.0.0/16
ipv4:
209.85.128.0/17
ipv4:
216.58.192.0/19
ipv4:
216.239.32.0/19
include:_netblocks2.google.com
v=spf1 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ~all
ipv6:
2001:4860:4000::/36
ipv6:
2404:6800:4000::/36
ipv6:
2607:f8b0:4000::/36
ipv6:
2800:3f0:4000::/36
ipv6:
2a00:1450:4000::/36
ipv6:
2c0f:fb50:4000::/36
include:_netblocks3.google.com
v=spf1 ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.253.56.0/21 ip4:172.253.112.0/20 ip4:108.177.96.0/19 ip4:35.191.0.0/16 ip4:130.211.0.0/22 ~all
ipv4:
172.217.0.0/19
ipv4:
172.217.32.0/20
ipv4:
172.217.128.0/19
ipv4:
172.217.160.0/20
ipv4:
172.217.192.0/19
ipv4:
172.253.56.0/21
ipv4:
172.253.112.0/20
ipv4:
108.177.96.0/19
ipv4:
35.191.0.0/16
ipv4:
130.211.0.0/22
include:spf.puntonet.cl
v=spf1 a ip4:200.75.30.33/27 ip6:2604:a880:4:1d0::119:8000 ip4:190.215.200.120/29 ip4:186.79.108.139 ip4:45.33.11.242 ip4:170.150.142.3 ip4:173.255.195.198 ip4:172.234.18.96 ip4:172.232.171.4 ip4:172.233.234.73 ip4:173.255.195.198 ip4:104.237.134.98 ip4:172.233.142.227 ip4:69.164.213.18 ip4:172.232.171.179 ip4:172.233.224.71 ip4:45.56.69.127 ip4:172.232.172.209 ip4:165.232.142.117 ip6:2600:3c00::f03c:93ff:fee4:acb8 ip6:2600:3c0a::f03c:93ff:fee4:92af ip6:2600:3c00::f03c:93ff:fee4:94a5 ip6:2600:3c00::f03c:93ff:fee1:0521 ip6:2600:3c06::f03c:93ff:fe6e:c0b1 ip6:2600:3c0a::f03c:93ff:fe6e:4d94 ip6:2600:3c05::f03c:93ff:fe73:fca6 ip6:2a01:7e03::f03c:93ff:fee4:2b41 ip6:2600:3c03::f03c:93ff:fee4:1739 ip6:2600:3c0a::f03c:93ff:fee4:2b0c ip6:2600:3c05::f03c:94ff:fe7a:8190 ~all
ipv4:
200.75.30.33/27
ipv4:
190.215.200.120/29
ipv4:
186.79.108.139
ipv4:
45.33.11.242
ipv4:
170.150.142.3
ipv4:
173.255.195.198
ipv4:
172.234.18.96
ipv4:
172.232.171.4
ipv4:
172.233.234.73
ipv4:
173.255.195.198
ipv4:
104.237.134.98
ipv4:
172.233.142.227
ipv4:
69.164.213.18
ipv4:
172.232.171.179
ipv4:
172.233.224.71
ipv4:
45.56.69.127
ipv4:
172.232.172.209
ipv4:
165.232.142.117
ipv6:
2604:a880:4:1d0::119:8000
ipv6:
2600:3c00::f03c:93ff:fee4:acb8
ipv6:
2600:3c0a::f03c:93ff:fee4:92af
ipv6:
2600:3c00::f03c:93ff:fee4:94a5
ipv6:
2600:3c00::f03c:93ff:fee1:0521
ipv6:
2600:3c06::f03c:93ff:fe6e:c0b1
ipv6:
2600:3c0a::f03c:93ff:fe6e:4d94
ipv6:
2600:3c05::f03c:93ff:fe73:fca6
ipv6:
2a01:7e03::f03c:93ff:fee4:2b41
ipv6:
2600:3c03::f03c:93ff:fee4:1739
ipv6:
2600:3c0a::f03c:93ff:fee4:2b0c
ipv6:
2600:3c05::f03c:94ff:fe7a:8190
unknown:

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

~all
SoftFail (non-compliant e-mails are accepted but marked)

Will be forwarded to another SPF record?

There is no reference to any other SPF record

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.

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 )

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:

172.67.144.67

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