SPF Check:
bis.org

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: 15 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

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

The SPF record analysis was performed on 04.05.2024 at 23:00:13 clock.

Lookup for the domain:
bis.org
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 bis.org 

Nameserverset:
dns4.p08.nsone.net
dns1.p08.nsone.net
ns0120.secondary.cloudflare.com
dns3.p08.nsone.net
ns0218.secondary.cloudflare.com
dns2.p08.nsone.net
Canonical names of the domain
okta.bis.org u18980060.wl061.sendgrid.net
Determined SPF record:
(u18980060.wl061.sendgrid.net)
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
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 
205.201.128.0/20
THEROCKETSCIENCEGROUP blacklist 
198.2.128.0/18
THEROCKETSCIENCEGROUP blacklist 
148.105.8.0/21
THEROCKETSCIENCEGROUP blacklist 
160.34.64.6 Oracle Svenska AB blacklist 
160.34.64.8 Oracle Svenska AB blacklist 
160.34.64.10 Oracle Svenska AB blacklist 
160.34.64.12 Oracle Svenska AB blacklist 
160.34.64.14 Oracle Svenska AB blacklist 
160.34.64.16 Oracle Svenska AB blacklist 
160.34.64.20 Oracle Svenska AB blacklist 
160.34.64.28 Oracle Svenska AB blacklist 
167.68.16.96 THOMSON-REUTERS blacklist 
167.68.17.96 THOMSON-REUTERS blacklist 
46.249.61.0/24
Serverius Holding B.V. blacklist 
159.183.193.109 SENDGRID blacklist 
159.183.200.101 SENDGRID blacklist 
159.183.213.105 SENDGRID blacklist 
159.183.213.107 SENDGRID blacklist 
159.183.213.204 SENDGRID blacklist 
159.183.214.96 SENDGRID blacklist 
167.89.110.192 SENDGRID blacklist 
167.89.126.180 SENDGRID blacklist 
50.31.57.204 SENDGRID blacklist 
52.50.129.119 AMAZON-02 blacklist 
54.174.209.165 AMAZON-AES blacklist 
52.16.75.109 AMAZON-02 blacklist 
52.16.75.118 AMAZON-02 blacklist 
52.16.38.44 AMAZON-02 blacklist 
52.16.49.62 AMAZON-02 blacklist 
54.79.0.4 AMAZON-02 blacklist 
35.182.195.41 AMAZON-02 blacklist 
54.85.129.207 AMAZON-AES blacklist 
52.22.249.69 AMAZON-AES blacklist 
18.197.43.76 AMAZON-02 blacklist 
54.93.104.220 AMAZON-02 blacklist 
3.209.231.65 AMAZON-AES blacklist 
34.206.143.108 AMAZON-AES blacklist 
35.157.192.122 AMAZON-02 blacklist 
18.132.189.127 AMAZON-02 blacklist 
52.65.244.27 AMAZON-02 blacklist 
15.223.142.138 AMAZON-02 blacklist 
3.248.148.18 AMAZON-02 blacklist 
107.20.91.250 AMAZON-AES blacklist 
3.96.249.213 AMAZON-02 blacklist 
52.58.159.50 AMAZON-02 blacklist 
3.11.129.102 AMAZON-02 blacklist 
34.242.156.53 AMAZON-02 blacklist 
52.4.156.8 AMAZON-AES blacklist 
34.251.63.7 AMAZON-02 blacklist 
52.64.32.126 AMAZON-02 blacklist 
193.108.136.0/23
NorthC Schweiz AG blacklist 
198.2.132.142 THEROCKETSCIENCEGROUP blacklist 
147.154.230.147 ORACLE-BMC-31898 blacklist 
138.1.16.88 ORACLE-BMC-31898 blacklist 
159.183.180.113 SENDGRID blacklist 
193.135.2.83 Bank for International Settlements (BIS) blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: bis.org

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized IPv4 addresses

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

193.108.136.0/23
198.2.132.142
147.154.230.147
138.1.16.88
159.183.180.113
193.135.2.83

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:servers.mcsv.net
v=spf1 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 -all
ipv4:
205.201.128.0/20
ipv4:
198.2.128.0/18
ipv4:
148.105.8.0/21
include:spf_ldx.taleo.net
v=spf1 ip4:160.34.64.6 ip4:160.34.64.8 ip4:160.34.64.10 ip4:160.34.64.12 ip4:160.34.64.14 ip4:160.34.64.16 ip4:160.34.64.20 ip4:160.34.64.28
ipv4:
160.34.64.6
ipv4:
160.34.64.8
ipv4:
160.34.64.10
ipv4:
160.34.64.12
ipv4:
160.34.64.14
ipv4:
160.34.64.16
ipv4:
160.34.64.20
ipv4:
160.34.64.28
include:_spf.westgroup.net
v=spf1 ip4:167.68.16.96 ip4:167.68.17.96 -all
ipv4:
167.68.16.96
ipv4:
167.68.17.96
include:_spf.qp-mail.eu
v=spf1 ip4:46.249.61.0/24 -all
ipv4:
46.249.61.0/24
include:okta.bis.org
v=spf1 ip4:159.183.193.109 ip4:159.183.200.101 ip4:159.183.213.105 ip4:159.183.213.107 ip4:159.183.213.204 ip4:159.183.214.96 ip4:167.89.110.192 ip4:167.89.126.180 ip4:50.31.57.204 -all
ipv4:
159.183.193.109
ipv4:
159.183.200.101
ipv4:
159.183.213.105
ipv4:
159.183.213.107
ipv4:
159.183.213.204
ipv4:
159.183.214.96
ipv4:
167.89.110.192
ipv4:
167.89.126.180
ipv4:
50.31.57.204
include:docebosaas.com
v=spf1 ip4:52.50.129.119 ip4:54.174.209.165 ip4:52.16.75.109 ip4:52.16.75.118 ip4:52.16.38.44 ip4:52.16.49.62 ip4:54.79.0.4 ip4:35.182.195.41 ip4:54.85.129.207 ip4:52.22.249.69 ip4:18.197.43.76 ip4:54.93.104.220 ip4:3.209.231.65 ip4:34.206.143.108 ip4:35.157.192.122 ip4:18.132.189.127 ip4:52.65.244.27 ip4:15.223.142.138 ip4:3.248.148.18 ip4:107.20.91.250 ip4:3.96.249.213 ip4:52.58.159.50 ip4:3.11.129.102 ip4:34.242.156.53 ip4:52.4.156.8 ip4:34.251.63.7 ip4:52.64.32.126 ~all
ipv4:
52.50.129.119
ipv4:
54.174.209.165
ipv4:
52.16.75.109
ipv4:
52.16.75.118
ipv4:
52.16.38.44
ipv4:
52.16.49.62
ipv4:
54.79.0.4
ipv4:
35.182.195.41
ipv4:
54.85.129.207
ipv4:
52.22.249.69
ipv4:
18.197.43.76
ipv4:
54.93.104.220
ipv4:
3.209.231.65
ipv4:
34.206.143.108
ipv4:
35.157.192.122
ipv4:
18.132.189.127
ipv4:
52.65.244.27
ipv4:
15.223.142.138
ipv4:
3.248.148.18
ipv4:
107.20.91.250
ipv4:
3.96.249.213
ipv4:
52.58.159.50
ipv4:
3.11.129.102
ipv4:
34.242.156.53
ipv4:
52.4.156.8
ipv4:
34.251.63.7
ipv4:
52.64.32.126

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

lb-mswsi.sitrox.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