SPF Check:
stlcc.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 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 stlcc.edu.
The SPF record for stlcc.edu 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 20.05.2024 at 18:45:48 clock.

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

Nameserverset:
ns1.stlcc.edu
ns2.stlcc.edu
Canonical names of the domain
email.gradesfirst.com sendgrid.net
Determined SPF record:
(sendgrid.net)
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
12.28.52.10/32
ATT-INTERNET4 blacklist 
12.234.216.10/32
ATT-INTERNET4 blacklist 
54.146.129.215/32
AMAZON-AES blacklist 
52.60.189.89/32
AMAZON-02 blacklist 
66.151.109.0/24
INTERNAP-BLK blacklist 
64.205.86.161/27
GTT Communications Inc. blacklist 
12.28.52.13/32
ATT-INTERNET4 blacklist 
198.187.196.100 TIS-DC1 blacklist 
52.45.50.190 AMAZON-AES blacklist 
52.42.20.3 AMAZON-02 blacklist 
52.31.29.196 AMAZON-02 blacklist 
52.60.142.64 AMAZON-02 blacklist 
13.237.94.13 AMAZON-02 blacklist 
52.76.190.252 AMAZON-02 blacklist 
3.218.253.173 AMAZON-AES blacklist 
35.160.78.215 AMAZON-02 blacklist 
3.99.6.92 AMAZON-02 blacklist 
54.195.228.99 AMAZON-02 blacklist 
13.215.187.237 AMAZON-02 blacklist 
54.66.240.63 AMAZON-02 blacklist 
208.117.49.214/32
SENDGRID blacklist 
104.45.175.206 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.224.142.128 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.180.90.234 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
208.117.61.155 SENDGRID blacklist 
162.209.88.57 RACKSPACE blacklist 
162.209.9.103 RACKSPACE blacklist 
23.253.183.124 RACKSPACE blacklist 
69.72.37.45 RACKSPACE blacklist 
69.72.44.77 AMAZON-02 blacklist 
69.72.38.99 MAILGUN blacklist 
69.72.34.206 RACKSPACE blacklist 
69.72.32.249 RACKSPACE blacklist 
143.55.227.129 MAILGUN blacklist 
146.20.191.120 RACKSPACE blacklist 
146.20.191.121 RACKSPACE blacklist 
146.20.191.122 RACKSPACE blacklist 
146.20.191.123 RACKSPACE blacklist 
146.20.191.34 RACKSPACE blacklist 
146.20.191.137 RACKSPACE blacklist 
159.135.232.81 RMH-14 blacklist 
166.78.71.248 RACKSPACE blacklist 
166.78.70.61 RACKSPACE blacklist 
167.89.0.0/17
SENDGRID blacklist 
208.117.48.0/20
SENDGRID blacklist 
50.31.32.0/19
SENDGRID blacklist 
198.37.144.0/20
SENDGRID blacklist 
198.21.0.0/21
SENDGRID blacklist 
192.254.112.0/20
SENDGRID blacklist 
168.245.0.0/17
SENDGRID blacklist 
149.72.0.0/16
AMAZON-AES blacklist 
159.183.0.0/16
SENDGRID blacklist 
223.165.113.0/24
SENDGRID blacklist 
223.165.115.0/24
SENDGRID blacklist 
223.165.118.0/23
SENDGRID blacklist 
223.165.120.0/23
SENDGRID 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::/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 
198.21.1.32/32
SENDGRID blacklist 
67.225.138.62/32
LIQUIDWEB blacklist 
208.75.120.0/22
ASN-CC blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: stlcc.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

12.28.52.10/32
12.234.216.10/32
54.146.129.215/32
52.60.189.89/32
66.151.109.0/24
64.205.86.161/27
12.28.52.13/32
198.187.196.100

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf1.stlcc.edu
v=spf1 include:spf.elluciancloud.com ip4:208.117.49.214/32 include:cust-spf.cashnet.com include:_spf.regroupcloud.com include:email.gradesfirst.com include:spf.protection.outlook.com ip4:198.21.1.32/32 ip4:67.225.138.62/32 ip4:208.75.120.0/22
ipv4:
208.117.49.214/32
ipv4:
198.21.1.32/32
ipv4:
67.225.138.62/32
ipv4:
208.75.120.0/22
include:spf.elluciancloud.com
v=spf1 ip4:52.45.50.190 ip4:52.42.20.3 ip4:52.31.29.196 ip4:52.60.142.64 ip4:13.237.94.13 ip4:52.76.190.252 ip4:3.218.253.173 ip4:35.160.78.215 ip4:3.99.6.92 ip4:54.195.228.99 ip4:13.215.187.237 ip4:54.66.240.63 ~all
ipv4:
52.45.50.190
ipv4:
52.42.20.3
ipv4:
52.31.29.196
ipv4:
52.60.142.64
ipv4:
13.237.94.13
ipv4:
52.76.190.252
ipv4:
3.218.253.173
ipv4:
35.160.78.215
ipv4:
3.99.6.92
ipv4:
54.195.228.99
ipv4:
13.215.187.237
ipv4:
54.66.240.63
include:cust-spf.cashnet.com
v=spf1 ip4:104.45.175.206 ip4:52.224.142.128 ip4:52.180.90.234 ip4:208.117.61.155 -all
ipv4:
104.45.175.206
ipv4:
52.224.142.128
ipv4:
52.180.90.234
ipv4:
208.117.61.155
include:_spf.regroupcloud.com
v=spf1 ip4:162.209.88.57 ip4:162.209.9.103 ip4:23.253.183.124 ip4:69.72.37.45 ip4:69.72.44.77 ip4:69.72.38.99 ip4:69.72.34.206 ip4:69.72.32.249 ip4:143.55.227.129 ip4:146.20.191.120 ip4:146.20.191.121 ip4:146.20.191.122 ip4:146.20.191.123 ip4:146.20.191.34 ip4:146.20.191.137 ip4:159.135.232.81 ip4:166.78.71.248 ip4:166.78.70.61 ~all
ipv4:
162.209.88.57
ipv4:
162.209.9.103
ipv4:
23.253.183.124
ipv4:
69.72.37.45
ipv4:
69.72.44.77
ipv4:
69.72.38.99
ipv4:
69.72.34.206
ipv4:
69.72.32.249
ipv4:
143.55.227.129
ipv4:
146.20.191.120
ipv4:
146.20.191.121
ipv4:
146.20.191.122
ipv4:
146.20.191.123
ipv4:
146.20.191.34
ipv4:
146.20.191.137
ipv4:
159.135.232.81
ipv4:
166.78.71.248
ipv4:
166.78.70.61
unknown:
include:email.gradesfirst.com
v=spf1 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 include:ab.sendgrid.net ~all
ipv4:
167.89.0.0/17
ipv4:
208.117.48.0/20
ipv4:
50.31.32.0/19
ipv4:
198.37.144.0/20
ipv4:
198.21.0.0/21
ipv4:
192.254.112.0/20
ipv4:
168.245.0.0/17
ipv4:
149.72.0.0/16
ipv4:
159.183.0.0/16
include:ab.sendgrid.net
v=spf1 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ~all
ipv4:
223.165.113.0/24
ipv4:
223.165.115.0/24
ipv4:
223.165.118.0/23
ipv4:
223.165.120.0/23
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

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:

12.28.52.1

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