SPF Check:
wyntec.net.au

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 wyntec.net.au.
The SPF record for wyntec.net.au 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, 64 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 16.04.2024 at 16:06:17 clock.

Lookup for the domain:
wyntec.net.au
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 wyntec.net.au 

Nameserverset:
pat.ns.cloudflare.com
neil.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
172.67.195.145 CLOUDFLARENET blacklist 
104.21.52.50 - CLOUDFLARENET 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/14
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.175.226.230/32
AMAZON-AES blacklist 
54.175.120.115/32
AMAZON-AES blacklist 
54.84.157.192/32
AMAZON-AES blacklist 
54.173.41.109/32
AMAZON-AES blacklist 
54.86.73.129/32
AMAZON-AES blacklist 
63.150.4.232/31
CENTURYLINK-US-LEGACY-QWEST blacklist 
100.42.120.128/27
SWITCH-LTD blacklist 
100.42.115.0/27
- blacklist 
69.84.129.224/27
COLOSPACE blacklist 
54.66.220.193/32
AMAZON-02 blacklist 
54.66.200.109/32
AMAZON-02 blacklist 
54.77.78.8/32
AMAZON-02 blacklist 
54.77.200.220/32
AMAZON-02 blacklist 
207.58.147.64/28
LEASEWEB-USA-WDC blacklist 
216.22.15.224/27
LEASEWEB-USA-WDC blacklist 
43.228.184.0/22
Arelion Sweden AB blacklist 
103.47.204.0/22
Arelion Sweden AB blacklist 
103.2.140.0/22
SERVERCENTRAL blacklist 
203.31.36.0/22
SERVERCENTRAL blacklist 
170.10.68.0/22
Wholesale Services Provider blacklist 
158.120.80.0/21
SERVERCENTRAL blacklist 
20.70.88.141 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.70.186.218 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.147.56.124 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.147.60.132 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.190.127.76 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
3.105.81.69 AMAZON-02 blacklist 
35.169.232.245 AMAZON-AES blacklist 
52.45.247.137 AMAZON-AES blacklist 
3.24.56.135 AMAZON-02 blacklist 
52.63.166.203 AMAZON-02 blacklist 
3.104.195.181 AMAZON-02 blacklist 
52.64.111.90 AMAZON-02 blacklist 
54.66.10.162 AMAZON-02 blacklist 
13.238.252.82 AMAZON-02 blacklist 
54.79.63.66 AMAZON-02 blacklist 
203.21.125.32 Wholesale Services Provider blacklist 
203.21.125.33 Wholesale Services Provider blacklist 
50.23.252.166 SOFTLAYER blacklist 
50.23.246.238 SOFTLAYER blacklist 
108.168.255.216 SOFTLAYER blacklist 
108.168.255.217 SOFTLAYER blacklist 
20.92.218.92 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.92.133.122 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.92.133.252 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.53.112.187 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.92.134.58 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.238.162.196 AMAZON-02 blacklist 
13.236.218.216 AMAZON-02 blacklist 
103.80.245.40 ACCESS 4 PTY LTD blacklist 
103.80.246.40 ACCESS 4 PTY LTD blacklist 
18.219.199.40 AMAZON-02 blacklist 
43.250.142.131 SYNERGY WHOLESALE PTY LTD blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: wyntec.net.au

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.195.145
104.21.52.50

Additionally authorized IPv4 addresses

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

103.80.245.40
103.80.246.40
18.219.199.40
43.250.142.131

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/14 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/14
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.myconnectwise.net
v=spf1 ip4:54.175.226.230/32 ip4:54.175.120.115/32 ip4:54.84.157.192/32 ip4:54.173.41.109/32 ip4:54.86.73.129/32 ip4:63.150.4.232/31 ip4:100.42.120.128/27 ip4:100.42.115.0/27 ip4:69.84.129.224/27 ip4:54.66.220.193/32 ip4:54.66.200.109/32 ip4:54.77.78.8/32 ip4:54.77.200.220/32 include:spf.smtp2go.com ~all
ipv4:
54.175.226.230/32
ipv4:
54.175.120.115/32
ipv4:
54.84.157.192/32
ipv4:
54.173.41.109/32
ipv4:
54.86.73.129/32
ipv4:
63.150.4.232/31
ipv4:
100.42.120.128/27
ipv4:
100.42.115.0/27
ipv4:
69.84.129.224/27
ipv4:
54.66.220.193/32
ipv4:
54.66.200.109/32
ipv4:
54.77.78.8/32
ipv4:
54.77.200.220/32
include:spf.smtp2go.com
v=spf1 ip4:207.58.147.64/28 ip4:216.22.15.224/27 ip4:43.228.184.0/22 ip4:103.47.204.0/22 ip4:103.2.140.0/22 ip4:203.31.36.0/22 ip4:170.10.68.0/22 ip4:158.120.80.0/21 ~all
ipv4:
207.58.147.64/28
ipv4:
216.22.15.224/27
ipv4:
43.228.184.0/22
ipv4:
103.47.204.0/22
ipv4:
103.2.140.0/22
ipv4:
203.31.36.0/22
ipv4:
170.10.68.0/22
ipv4:
158.120.80.0/21
include:customer.mailguard.com.au
v=spf1 include:spf_b.mailguard.com.au ip4:3.24.56.135 ip4:52.63.166.203 ip4:3.104.195.181 ip4:52.64.111.90 ip4:54.66.10.162 ip4:13.238.252.82 ip4:54.79.63.66 include:spf_a.mailguard.com.au -all
ipv4:
3.24.56.135
ipv4:
52.63.166.203
ipv4:
3.104.195.181
ipv4:
52.64.111.90
ipv4:
54.66.10.162
ipv4:
13.238.252.82
ipv4:
54.79.63.66
include:spf_b.mailguard.com.au
v=spf1 ip4:20.70.88.141 ip4:13.70.186.218 ip4:52.147.56.124 ip4:52.147.60.132 ip4:20.190.127.76 ip4:3.105.81.69 ip4:35.169.232.245 ip4:52.45.247.137 -all
ipv4:
20.70.88.141
ipv4:
13.70.186.218
ipv4:
52.147.56.124
ipv4:
52.147.60.132
ipv4:
20.190.127.76
ipv4:
3.105.81.69
ipv4:
35.169.232.245
ipv4:
52.45.247.137
include:spf_a.mailguard.com.au
v=spf1 ip4:203.21.125.32 ip4:203.21.125.33 ip4:50.23.252.166 ip4:50.23.246.238 ip4:108.168.255.216 ip4:108.168.255.217 ip4:20.92.218.92 ip4:20.92.133.122 ip4:20.92.133.252 ip4:20.53.112.187 ip4:20.92.134.58 ip4:13.238.162.196 ip4:13.236.218.216 -all
ipv4:
203.21.125.32
ipv4:
203.21.125.33
ipv4:
50.23.252.166
ipv4:
50.23.246.238
ipv4:
108.168.255.216
ipv4:
108.168.255.217
ipv4:
20.92.218.92
ipv4:
20.92.133.122
ipv4:
20.92.133.252
ipv4:
20.53.112.187
ipv4:
20.92.134.58
ipv4:
13.238.162.196
ipv4:
13.236.218.216

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

104.21.52.50

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