SPF Check:
spworkflow.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 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 spworkflow.com.
The SPF record for spworkflow.com 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, 68 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 27.04.2024 at 22:42:26 clock.

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

Nameserverset:
ns43.domaincontrol.com
ns44.domaincontrol.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
15.197.142.173 AMAZON-02 blacklist 
3.33.152.147 AMAZON-02 blacklist 
142.250.110.26 GOOGLE blacklist 
2a00:1450:400c:c02:0:0:0:1a GOOGLE blacklist 
142.250.153.26 GOOGLE blacklist 
2a00:1450:4013:c16:0:0:0:1b GOOGLE blacklist 
142.251.9.26 GOOGLE blacklist 
2a00:1450:4025:c03:0:0:0:1a GOOGLE blacklist 
142.250.150.27 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 
147.135.114.119 OVH SAS blacklist 
135.148.66.226 OVH SAS blacklist 
15.204.149.240 OVH SAS blacklist 
15.204.149.241 OVH SAS blacklist 
15.204.149.242 OVH SAS blacklist 
15.204.165.173 OVH SAS blacklist 
15.204.165.174 OVH SAS blacklist 
15.204.165.178 OVH SAS blacklist 
51.81.29.86 OVH SAS blacklist 
51.81.29.87 OVH SAS blacklist 
51.81.52.67 OVH SAS blacklist 
51.81.68.185 OVH SAS blacklist 
51.81.71.154 OVH SAS blacklist 
147.135.102.136 OVH SAS blacklist 
51.81.137.233 OVH SAS blacklist 
51.81.195.95 OVH SAS blacklist 
51.81.195.96 OVH SAS blacklist 
51.81.195.97 OVH SAS blacklist 
51.81.182.205 OVH SAS blacklist 
51.81.182.220 OVH SAS blacklist 
51.81.137.176 OVH SAS blacklist 
51.81.140.24 OVH SAS blacklist 
51.81.137.195 OVH SAS blacklist 
51.81.137.225 OVH SAS blacklist 
51.81.137.239 OVH SAS blacklist 
147.135.40.5 OVH SAS blacklist 
51.81.140.31 OVH SAS blacklist 
51.81.137.244 OVH SAS blacklist 
15.204.59.74 OVH SAS 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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: spworkflow.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

15.197.142.173
3.33.152.147

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
alt1.aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com
alt4.aspmx.l.google.com

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.windifferent.com
v=spf1 ip4:147.135.114.119 ip4:135.148.66.226 ip4:15.204.149.240 ip4:15.204.149.241 ip4:15.204.149.242 ip4:15.204.165.173 ip4:15.204.165.174 ip4:15.204.165.178 ip4:51.81.29.86 ip4:51.81.29.87 ip4:51.81.52.67 ip4:51.81.68.185 ip4:51.81.71.154 ip4:147.135.102.136 ip4:51.81.137.233 ip4:51.81.195.95 ip4:51.81.195.96 ip4:51.81.195.97 ip4:51.81.182.205 ip4:51.81.182.220 ip4:51.81.137.176 ip4:51.81.140.24 ip4:51.81.137.195 ip4:51.81.137.225 ip4:51.81.137.239 ip4:147.135.40.5 ip4:51.81.140.31 ip4:51.81.137.244 ip4:15.204.59.74 -all
ipv4:
147.135.114.119
ipv4:
135.148.66.226
ipv4:
15.204.149.240
ipv4:
15.204.149.241
ipv4:
15.204.149.242
ipv4:
15.204.165.173
ipv4:
15.204.165.174
ipv4:
15.204.165.178
ipv4:
51.81.29.86
ipv4:
51.81.29.87
ipv4:
51.81.52.67
ipv4:
51.81.68.185
ipv4:
51.81.71.154
ipv4:
147.135.102.136
ipv4:
51.81.137.233
ipv4:
51.81.195.95
ipv4:
51.81.195.96
ipv4:
51.81.195.97
ipv4:
51.81.182.205
ipv4:
51.81.182.220
ipv4:
51.81.137.176
ipv4:
51.81.140.24
ipv4:
51.81.137.195
ipv4:
51.81.137.225
ipv4:
51.81.137.239
ipv4:
147.135.40.5
ipv4:
51.81.140.31
ipv4:
51.81.137.244
ipv4:
15.204.59.74
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

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:

a4ec4c6ea1c92e2e6.awsglobalaccelerator.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   Connected by Team Internet