SPF Check:
chla.usc.edu

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

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

The SPF record analysis was performed on 16.05.2024 at 06:21:30 clock.

Lookup for the domain:
chla.usc.edu
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 chla.usc.edu 

Nameserverset:
ns-1295.awsdns-33.org
ns-1701.awsdns-20.co.uk
ns-172.awsdns-21.com
ns-789.awsdns-34.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
104.193.219.11 - blacklist 
104.193.219.12 - blacklist 
216.71.144.128/25
IRONPORT-SYSTEMS-INC blacklist 
216.71.141.128/25
IRONPORT-SYSTEMS-INC blacklist 
72.10.184.102/31
HURONCG blacklist 
72.10.180.28/31
HURONCG blacklist 
129.146.141.125 ORACLE-BMC-31898 blacklist 
129.146.115.250 ORACLE-BMC-31898 blacklist 
129.213.52.209 ORACLE-BMC-31898 blacklist 
129.213.108.188 ORACLE-BMC-31898 blacklist 
216.235.195.0/24
BLACKBAUD-ASN blacklist 
74.123.153.0/25
BLACKBAUD-ASN blacklist 
74.123.154.128/25
BLACKBAUD-ASN blacklist 
64.244.120.32/27
XO-AS15 blacklist 
64.244.122.192/27
XO-AS15 blacklist 
216.235.195.128/27
BLACKBAUD-ASN blacklist 
216.235.195.160/27
BLACKBAUD-ASN blacklist 
205.139.104.0/22
CENTURYLINK-LEGACY-LVLT-203 blacklist 
208.75.120.0/22
ASN-CC blacklist 
205.207.104.0/22
ASN-CC 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::/50
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 
20.151.64.254 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.151.66.242 MICROSOFT-CORP-MSN-AS-BLOCK 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.19.0.156 AMAZON-02 blacklist 
3.97.56.230 AMAZON-02 blacklist 
18.233.211.170 AMAZON-AES blacklist 
68.232.135.234/31
IRONPORT-SYSTEMS-INC blacklist 
68.232.140.57 IRONPORT-SYSTEMS-INC blacklist 
68.232.140.79 IRONPORT-SYSTEMS-INC blacklist 
216.235.195.0/24
BLACKBAUD-ASN blacklist 
72.10.180.28 HURONCG blacklist 
72.10.180.29 HURONCG blacklist 
208.117.51.45 SENDGRID blacklist 
205.139.105.48/29
CENTURYLINK-LEGACY-LVLT-203 blacklist 
206.79.6.128/26
CENTURYLINK-LEGACY-LVLT-203 blacklist 
208.40.241.140/30
EXPEDIENT blacklist 
216.37.18.6 EXPEDIENT blacklist 
204.8.10.114 HRTC blacklist 
216.235.197.198 CENTURYLINK-LEGACY-LVLT-203 blacklist 
64.209.141.221 CENTURYLINK-LEGACY-LVLT-203 blacklist 
205.139.104.0/22
CENTURYLINK-LEGACY-LVLT-203 blacklist 
216.235.196.0/22
CENTURYLINK-LEGACY-LVLT-203 blacklist 
216.235.200.0/21
CENTURYLINK-LEGACY-LVLT-203 blacklist 
206.79.6.0/24
CENTURYLINK-LEGACY-LVLT-203 blacklist 
216.235.195.0/24
BLACKBAUD-ASN blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: chla.usc.edu

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

104.193.219.11
104.193.219.12
216.71.144.128/25
216.71.141.128/25
216.235.195.0/24
72.10.180.28
72.10.180.29
208.117.51.45

Additional external SPF records

We could find other records authorized in the SPF record

include:spf1.chla.usc.edu
v=spf1 include:spf3.chla.usc.edu include:outboundmail.convio.net ip4:208.75.120.0/22 ip4:205.207.104.0/22 include:spf-outlook.chla.usc.edu include:spf2.chla.usc.edu ~all
ipv4:
208.75.120.0/22
ipv4:
205.207.104.0/22
include:spf3.chla.usc.edu
v=spf1 ip4:72.10.184.102/31 ip4:72.10.180.28/31 ip4:129.146.141.125 ip4:129.146.115.250 ip4:129.213.52.209 ip4:129.213.108.188 ~all
ipv4:
72.10.184.102/31
ipv4:
72.10.180.28/31
ipv4:
129.146.141.125
ipv4:
129.146.115.250
ipv4:
129.213.52.209
ipv4:
129.213.108.188
include:outboundmail.convio.net
v=spf1 +ip4:216.235.195.0/24 +ip4:74.123.153.0/25 +ip4:74.123.154.128/25 +ip4:64.244.120.32/27 +ip4:64.244.122.192/27 +ip4:216.235.195.128/27 +ip4:216.235.195.160/27 +ip4:205.139.104.0/22 +include:sparkpostmail.com ~all
ipv4:
216.235.195.0/24
ipv4:
74.123.153.0/25
ipv4:
74.123.154.128/25
ipv4:
64.244.120.32/27
ipv4:
64.244.122.192/27
ipv4:
216.235.195.128/27
ipv4:
216.235.195.160/27
ipv4:
205.139.104.0/22
unknown:
+include:sparkpostmail.com
include:spf-outlook.chla.usc.edu
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::/50 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::/50
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52
include:spf2.chla.usc.edu
v=spf1 ip4:20.151.64.254 ip4:20.151.66.242 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.19.0.156 ip4:3.97.56.230 ip4:18.233.211.170 ip4:68.232.135.234/31 ip4:68.232.140.57 ip4:68.232.140.79 ~all
ipv4:
20.151.64.254
ipv4:
20.151.66.242
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.19.0.156
ipv4:
3.97.56.230
ipv4:
18.233.211.170
ipv4:
68.232.135.234/31
ipv4:
68.232.140.57
ipv4:
68.232.140.79
include:spf-blackbaud.chla.usc.edu
v=spf1 ip4:205.139.105.48/29 ip4:206.79.6.128/26 ip4:208.40.241.140/30 ip4:216.37.18.6 ip4:204.8.10.114 ip4:216.235.197.198 ip4:64.209.141.221 ip4:205.139.104.0/22 ip4:216.235.196.0/22 ip4:216.235.200.0/21 ip4:206.79.6.0/24 ip4:216.235.195.0/24 ~all
ipv4:
205.139.105.48/29
ipv4:
206.79.6.128/26
ipv4:
208.40.241.140/30
ipv4:
216.37.18.6
ipv4:
204.8.10.114
ipv4:
216.235.197.198
ipv4:
64.209.141.221
ipv4:
205.139.104.0/22
ipv4:
216.235.196.0/22
ipv4:
216.235.200.0/21
ipv4:
206.79.6.0/24
ipv4:
216.235.195.0/24

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:

128.125.179.52

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