SPF Check:
concordiahcbs.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 passed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 0 errors
  •   Email Anti-Spoofing: Good

Your overall domain security

SPF is only one of 11 security factors. Your domain still has critical gaps.

Email authentication
SPF DKIM ? DMARC ?
Email transport
TLS ? MTA-STS ? TLSRPT ? DANE ?
Reputation
DNSBL ? BIMI ?
Certificate control
DNSSEC ? CAA ?
Summary of the SPF check

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

The SPF record analysis was performed on 11.06.2026 at 05:53:51 clock.

Lookup for the domain:
concordiahcbs.org
IP address to be checked:
no IP address specified
Find out now: The BSI's Email Security Year 2025
This way, you'll be well prepared and can now strengthen your email security in a targeted manner.
Find out now: The BSI's Email Security Year 2025

Evaluation for the domain concordiahcbs.org 

Nameserverset:
ns30.worldnic.com
ns29.worldnic.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
24.101.31.147 Armstrong blacklist 
50.221.234.242 Comcast Cable Communications, LLC blacklist 
72.23.249.250 Armstrong blacklist 
66.37.63.154 Fidium blacklist 
50.199.162.185 Comcast Cable Communications, LLC blacklist 
96.89.34.61 Comcast Cable Communications, LLC blacklist 
24.101.31.146 Armstrong blacklist 
97.79.31.98 Charter Communications, Inc blacklist 
24.101.152.75 Armstrong blacklist 
206.193.229.194 Fidium blacklist 
70.88.174.21 Comcast Cable Communications, LLC blacklist 
70.89.104.178 Comcast Cable Communications, LLC blacklist 
24.154.244.24 Armstrong blacklist 
208.103.119.146 DQE Communications LLC blacklist 
50.248.83.105 Comcast Cable Communications, LLC blacklist 
24.154.179.59 Armstrong blacklist 
173.13.32.165 Comcast Cable Communications, LLC blacklist 
96.66.170.81 Comcast Cable Communications, LLC blacklist 
24.154.120.240 Armstrong blacklist 
50.197.39.233 Comcast Cable Communications, LLC blacklist 
96.69.89.73 Comcast Cable Communications, LLC blacklist 
74.62.109.2 Charter Communications Inc blacklist 
24.154.55.161 Armstrong blacklist 
50.243.177.33 Comcast Cable Communications, LLC blacklist 
50.188.0.217 Comcast Cable Communications, LLC blacklist 
50.188.0.213 Comcast Cable Communications, LLC blacklist 
96.89.41.73 Comcast Cable Communications, LLC blacklist 
216.71.147.165 Cisco Systems Ironport Division blacklist 
40.92.0.0/15
Microsoft Corporation blacklist 
40.107.0.0/16
Microsoft Corporation blacklist 
52.100.0.0/15
Microsoft Corporation blacklist 
52.102.0.0/16
Microsoft Corporation blacklist 
52.103.0.0/17
Microsoft Corporation blacklist 
104.47.0.0/17
Microsoft Corporation blacklist 
2a01:111:f400::/48
Microsoft Corporation blacklist 
2a01:111:f403::/49
Microsoft Corporation blacklist 
2a01:111:f403:8000::/51
Microsoft Corporation blacklist 
2a01:111:f403:c000::/51
Microsoft Corporation blacklist 
2a01:111:f403:f000::/52
Microsoft Corporation blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: concordiahcbs.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

24.101.31.147
50.221.234.242
72.23.249.250
66.37.63.154
50.199.162.185
96.89.34.61
24.101.31.146
97.79.31.98
24.101.152.75
206.193.229.194
70.88.174.21
70.89.104.178
24.154.244.24
208.103.119.146
50.248.83.105
24.154.179.59
173.13.32.165
96.66.170.81
24.154.120.240
50.197.39.233
96.69.89.73
74.62.109.2
24.154.55.161
50.243.177.33
50.188.0.217
50.188.0.213
96.89.41.73
216.71.147.165

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/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 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/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
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

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

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:

208.91.197.27

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.
© 2026 nicmanager.com.   All rights reserved.
nicmanager