SPF Check:
bioiq.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 failed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 7 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

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

The SPF record analysis was performed on 23.12.2024 at 01:58:07 clock.

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

Nameserverset:
fish.ns.cloudflare.com
chip.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
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 
4.7.16.128/26
LEVEL3 blacklist 
38.108.186.0/24
COGENT-174 blacklist 
199.87.209.0/24
SV3-AS-PRI blacklist 
4.53.200.128/26
LEVEL3 blacklist 
52.62.199.66 AMAZON-02 blacklist 
52.63.210.175 AMAZON-02 blacklist 
52.19.0.156 AMAZON-02 blacklist 
34.242.34.203 AMAZON-02 blacklist 
15.157.154.20 AMAZON-02 blacklist 
3.97.56.230 AMAZON-02 blacklist 
18.233.211.170 AMAZON-AES blacklist 
18.210.219.222 AMAZON-AES blacklist 
16.50.78.62 AMAZON-02 blacklist 
16.51.180.22 AMAZON-02 blacklist 
18.196.254.50 AMAZON-02 blacklist 
3.75.50.121 AMAZON-02 blacklist 
40.176.107.168 AMAZON-02 blacklist 
40.176.215.184 AMAZON-02 blacklist 
20.109.99.74 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.97.237.150 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.122.187.209 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.10.6.183 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.1.175.150 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.209.145.54 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
18.198.129.203 AMAZON-02 blacklist 
52.52.134.28 AMAZON-02 blacklist 
18.222.100.37 AMAZON-02 blacklist 
18.220.6.173 AMAZON-02 blacklist 
13.89.129.61 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.86.47.187 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
34.211.36.37 AMAZON-02 blacklist 
34.209.22.161 AMAZON-02 blacklist 
18.219.211.170 AMAZON-02 blacklist 
52.179.183.89 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.88.170.98 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.192.29.133 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
44.240.143.150 AMAZON-02 blacklist 
52.52.30.41 AMAZON-02 blacklist 
54.203.18.106 AMAZON-02 blacklist 
20.65.115.153 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.165.249.35 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.242.106.212 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.252.111.27 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.214.168.26 AMAZON-02 blacklist 
209.61.151.0/24
RMH-14 blacklist 
166.78.68.0/22
RACKSPACE blacklist 
198.61.254.0/23
RACKSPACE blacklist 
192.237.158.0/23
RACKSPACE blacklist 
23.253.182.0/23
RACKSPACE blacklist 
104.130.96.0/28
RACKSPACE blacklist 
146.20.113.0/24
RACKSPACE blacklist 
146.20.191.0/24
RACKSPACE blacklist 
159.135.224.0/20
MAILGUN blacklist 
69.72.32.0/20
MAILGUN blacklist 
104.130.122.0/23
RACKSPACE blacklist 
146.20.112.0/26
RACKSPACE blacklist 
161.38.192.0/20
MAILGUN blacklist 
143.55.224.0/21
MAILGUN blacklist 
143.55.232.0/22
MAILGUN blacklist 
159.112.240.0/20
MAILGUN blacklist 
198.244.48.0/20
MAILGUN blacklist 
204.220.168.0/21
VOYANT blacklist 
204.220.176.0/20
MAILGUN blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: bioiq.com

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:_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.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
include:_spf.intacct.com
v=spf1 ip4:4.7.16.128/26 ip4:38.108.186.0/24 ip4:199.87.209.0/24 ip4:4.53.200.128/26 ip4:52.62.199.66 ip4:52.63.210.175 ip4:52.19.0.156 ip4:34.242.34.203 ip4:15.157.154.20 ip4:3.97.56.230 ip4:18.233.211.170 ip4:18.210.219.222 ip4:16.50.78.62 ip4:16.51.180.22 ip4:18.196.254.50 ip4:3.75.50.121 ip4:40.176.107.168 ip4:40.176.215.184 ip4:20.109.99.74 ip4:20.97.237.150 ip4:20.122.187.209 ip4:20.10.6.183 ip4:20.1.175.150 ip4:104.209.145.54 ip4:18.198.129.203 ip4:52.52.134.28 ip4:18.222.100.37 ip4:18.220.6.173 ip4:13.89.129.61 ip4:40.86.47.187 ip4:34.211.36.37 ip4:34.209.22.161 ip4:18.219.211.170 ip4:52.179.183.89 ip4:13.88.170.98 ip4:20.192.29.133 ip4:44.240.143.150 ip4:52.52.30.41 ip4:54.203.18.106 ip4:20.65.115.153 ip4:52.165.249.35 ip4:20.242.106.212 ip4:52.252.111.27 ip4:52.214.168.26 ?all
ipv4:
4.7.16.128/26
ipv4:
38.108.186.0/24
ipv4:
199.87.209.0/24
ipv4:
4.53.200.128/26
ipv4:
52.62.199.66
ipv4:
52.63.210.175
ipv4:
52.19.0.156
ipv4:
34.242.34.203
ipv4:
15.157.154.20
ipv4:
3.97.56.230
ipv4:
18.233.211.170
ipv4:
18.210.219.222
ipv4:
16.50.78.62
ipv4:
16.51.180.22
ipv4:
18.196.254.50
ipv4:
3.75.50.121
ipv4:
40.176.107.168
ipv4:
40.176.215.184
ipv4:
20.109.99.74
ipv4:
20.97.237.150
ipv4:
20.122.187.209
ipv4:
20.10.6.183
ipv4:
20.1.175.150
ipv4:
104.209.145.54
ipv4:
18.198.129.203
ipv4:
52.52.134.28
ipv4:
18.222.100.37
ipv4:
18.220.6.173
ipv4:
13.89.129.61
ipv4:
40.86.47.187
ipv4:
34.211.36.37
ipv4:
34.209.22.161
ipv4:
18.219.211.170
ipv4:
52.179.183.89
ipv4:
13.88.170.98
ipv4:
20.192.29.133
ipv4:
44.240.143.150
ipv4:
52.52.30.41
ipv4:
54.203.18.106
ipv4:
20.65.115.153
ipv4:
52.165.249.35
ipv4:
20.242.106.212
ipv4:
52.252.111.27
ipv4:
52.214.168.26
unknown:
include:_spf.mailgun.org
v=spf1 include:_spf1.mailgun.org include:_spf2.mailgun.org ~all
include:_spf1.mailgun.org
v=spf1 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ~all
ipv4:
209.61.151.0/24
ipv4:
166.78.68.0/22
ipv4:
198.61.254.0/23
ipv4:
192.237.158.0/23
ipv4:
23.253.182.0/23
ipv4:
104.130.96.0/28
ipv4:
146.20.113.0/24
ipv4:
146.20.191.0/24
ipv4:
159.135.224.0/20
ipv4:
69.72.32.0/20
include:_spf2.mailgun.org
v=spf1 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ~all
ipv4:
104.130.122.0/23
ipv4:
146.20.112.0/26
ipv4:
161.38.192.0/20
ipv4:
143.55.224.0/21
ipv4:
143.55.232.0/22
ipv4:
159.112.240.0/20
ipv4:
198.244.48.0/20
ipv4:
204.220.168.0/21
ipv4:
204.220.176.0/20

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:

172.67.140.234

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