SPF Check:
advancement.kennesaw.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 advancement.kennesaw.edu.
The SPF record for advancement.kennesaw.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, 35 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 16.11.2024 at 23:34:07 clock.

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

Nameserverset:
kennns-16.kennesaw.edu
kenn-ns01.kennesaw.edu
kenn-ns02.kennesaw.edu
kennns-15.kennesaw.edu
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
216.235.195.0/24
BLACKBAUD-ASN 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 - 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
- blacklist 
216.235.200.0/21
CENTURYLINK-LEGACY-LVLT-203 blacklist 
216.235.195.0/24
BLACKBAUD-ASN blacklist 
69.75.152.160/28
TWC-20001-PACWEST blacklist 
34.215.115.241 AMAZON-02 blacklist 
159.135.228.232 MAILGUN blacklist 
159.135.232.65 MAILGUN blacklist 
161.38.193.223 MAILGUN blacklist 
161.38.193.230 MAILGUN blacklist 
161.38.193.235 MAILGUN blacklist 
161.38.194.153 MAILGUN blacklist 
161.38.194.172 MAILGUN blacklist 
161.38.194.198 MAILGUN blacklist 
198.244.48.135 MAILGUN blacklist 
161.38.193.170 MAILGUN 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/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.102.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.103.0.0/17
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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: advancement.kennesaw.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

216.235.195.0/24

Additional external SPF records

We could find other records authorized in the SPF record

include:outboundmail.blackbaud.net
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:216.235.195.0/24 exists:%{i}._spf.sparkpostmail.com ~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:
216.235.195.0/24
include:secure.giftlegacy.com
v=spf1 ip4:69.75.152.160/28 ip4:34.215.115.241 ip4:159.135.228.232 ip4:159.135.232.65 ip4:161.38.193.223 ip4:161.38.193.230 ip4:161.38.193.235 ip4:161.38.194.153 ip4:161.38.194.172 ip4:161.38.194.198 ip4:198.244.48.135 ip4:161.38.193.170 -all
ipv4:
69.75.152.160/28
ipv4:
34.215.115.241
ipv4:
159.135.228.232
ipv4:
159.135.232.65
ipv4:
161.38.193.223
ipv4:
161.38.193.230
ipv4:
161.38.193.235
ipv4:
161.38.194.153
ipv4:
161.38.194.172
ipv4:
161.38.194.198
ipv4:
198.244.48.135
ipv4:
161.38.193.170
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:

No PTR record found

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