SPF Check:
visiontravel.ca

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
Summary of the SPF check

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

The SPF record analysis was performed on 23.12.2024 at 12:32:29 clock.

Lookup for the domain:
visiontravel.ca
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 visiontravel.ca 

Nameserverset:
ns1-02.azure-dns.com
ns2-02.azure-dns.net
ns3-02.azure-dns.org
ns4-02.azure-dns.info
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
12.129.35.0/27
ATT-INTERNET4 blacklist 
13.64.55.16/28
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.100.16.236 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.100.38.75 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.249.208.0/20
AMAZON-02 blacklist 
23.251.224.0/19
AMAZON-02 blacklist 
34.196.97.243 AMAZON-AES blacklist 
40.92.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.107.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
50.31.62.176 SENDGRID blacklist 
51.77.79.158 OVH SAS blacklist 
51.89.119.103 OVH SAS 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 
52.226.94.192/28
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 
54.36.149.183 OVH SAS blacklist 
54.38.221.122 OVH SAS blacklist 
54.240.0.0/17
AMAZON-02 blacklist 
64.17.5.11 DATABANK-ZCOLO blacklist 
64.34.128.109 COGECO-PEER1 blacklist 
66.147.244.139 UNIFIEDLAYER-AS-1 blacklist 
66.180.72.0/21
SACATECH blacklist 
67.136.129.6 ABUL-14-7385 blacklist 
69.169.224.0/20
AMAZON-02 blacklist 
72.138.68.200 ROGERS-COMMUNICATIONS blacklist 
72.249.160.11 AS17378 blacklist 
72.249.160.12 AS17378 blacklist 
74.91.88.135 MOZGROUP-SMTP blacklist 
74.91.89.17 MOZGROUP-SMTP blacklist 
74.113.72.0/22
SOFTVOYAGE-NET blacklist 
76.223.128.0/19
AMAZON-02 blacklist 
76.223.176.0/20
AMAZON-02 blacklist 
79.135.106.0/23
Proton AG blacklist 
91.134.188.129 OVH SAS blacklist 
97.74.42.79 AS-26496-GO-DADDY-COM-LLC blacklist 
104.47.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.209.35.28 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
151.193.0.0/16
GOOGLE-CLOUD-PLATFORM blacklist 
169.145.39.240/29
SAP-DC-NS blacklist 
173.45.98.172 ENET-2 blacklist 
185.70.40.0/23
Proton AG blacklist 
185.70.43.0/24
Proton AG blacklist 
188.165.51.139 OVH SAS blacklist 
191.237.4.149 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
199.122.112.0/22
SACATECH blacklist 
199.127.232.0/22
AMAZON-02 blacklist 
199.255.192.0/22
AMAZON-02 blacklist 
206.55.144.0/20
AMAZON-02 blacklist 
207.167.196.15 TELUS Communications blacklist 
216.221.160.0/19
AMAZON-02 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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: visiontravel.ca

SPF record available?

We found an SPF record for the domain.

v=spf1

Additional external SPF records

We could find other records authorized in the SPF record

include:_s47498958.fdmarc.net
v=spf1 exists:_i.%{i}._o.%{o}._d.%{d}._l.%{l}._h.%{h}._f.47498958.7.4.fdmarc.net exists:%{i}._spf.mta.salesforce.com ip4:12.129.35.0/27 ip4:13.64.55.16/28 ip4:23.100.16.236 ip4:23.100.38.75 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:34.196.97.243 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:50.31.62.176 ip4:51.77.79.158 ip4:51.89.119.103 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 include:_s474989580.fdmarc.net -all
ipv4:
12.129.35.0/27
ipv4:
13.64.55.16/28
ipv4:
23.100.16.236
ipv4:
23.100.38.75
ipv4:
23.249.208.0/20
ipv4:
23.251.224.0/19
ipv4:
34.196.97.243
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
50.31.62.176
ipv4:
51.77.79.158
ipv4:
51.89.119.103
ipv4:
52.100.0.0/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
include:_s474989580.fdmarc.net
v=spf1 ip4:52.226.94.192/28 ip4:52.233.37.155 ip4:52.242.32.10 ip4:54.36.149.183 ip4:54.38.221.122 ip4:54.240.0.0/17 ip4:64.17.5.11 ip4:64.34.128.109 ip4:66.147.244.139 ip4:66.180.72.0/21 ip4:67.136.129.6 ip4:69.169.224.0/20 ip4:72.138.68.200 ip4:72.249.160.11 ip4:72.249.160.12 ip4:74.91.88.135 ip4:74.91.89.17 ip4:74.113.72.0/22 ip4:76.223.128.0/19 ip4:76.223.176.0/20 ip4:79.135.106.0/23 include:_s474989581.fdmarc.net -all
ipv4:
52.226.94.192/28
ipv4:
52.233.37.155
ipv4:
52.242.32.10
ipv4:
54.36.149.183
ipv4:
54.38.221.122
ipv4:
54.240.0.0/17
ipv4:
64.17.5.11
ipv4:
64.34.128.109
ipv4:
66.147.244.139
ipv4:
66.180.72.0/21
ipv4:
67.136.129.6
ipv4:
69.169.224.0/20
ipv4:
72.138.68.200
ipv4:
72.249.160.11
ipv4:
72.249.160.12
ipv4:
74.91.88.135
ipv4:
74.91.89.17
ipv4:
74.113.72.0/22
ipv4:
76.223.128.0/19
ipv4:
76.223.176.0/20
ipv4:
79.135.106.0/23
include:_s474989581.fdmarc.net
v=spf1 ip4:91.134.188.129 ip4:97.74.42.79 ip4:104.47.0.0/17 ip4:104.209.35.28 ip4:151.193.0.0/16 ip4:169.145.39.240/29 ip4:173.45.98.172 ip4:185.70.40.0/23 ip4:185.70.43.0/24 ip4:188.165.51.139 ip4:191.237.4.149 ip4:199.122.112.0/22 ip4:199.127.232.0/22 ip4:199.255.192.0/22 ip4:206.55.144.0/20 ip4:207.167.196.15 ip4:216.221.160.0/19 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 include:_s474989582.fdmarc.net -all
ipv4:
91.134.188.129
ipv4:
97.74.42.79
ipv4:
104.47.0.0/17
ipv4:
104.209.35.28
ipv4:
151.193.0.0/16
ipv4:
169.145.39.240/29
ipv4:
173.45.98.172
ipv4:
185.70.40.0/23
ipv4:
185.70.43.0/24
ipv4:
188.165.51.139
ipv4:
191.237.4.149
ipv4:
199.122.112.0/22
ipv4:
199.127.232.0/22
ipv4:
199.255.192.0/22
ipv4:
206.55.144.0/20
ipv4:
207.167.196.15
ipv4:
216.221.160.0/19
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
include:_s474989582.fdmarc.net
v=spf1 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52

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

20.175.159.104

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