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

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

The SPF record analysis was performed on 05.05.2024 at 10:17:43 clock.

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

Nameserverset:
usmiaa1ns03.ithaka.org
usnjpr2ns01.ithaka.org
usnjpr2ns02.ithaka.org
usnjpr2ns04.ithaka.org
usnyny1ns05.ithaka.org
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
68.232.154.47 IRONPORT-SYSTEMS-INC blacklist 
68.232.140.152 IRONPORT-SYSTEMS-INC blacklist 
68.232.140.152 IRONPORT-SYSTEMS-INC blacklist 
68.232.154.47 IRONPORT-SYSTEMS-INC blacklist 
68.232.154.47 IRONPORT-SYSTEMS-INC blacklist 
68.232.140.152 IRONPORT-SYSTEMS-INC blacklist 
72.46.76.0/22
ACTON-SOFTWARE blacklist 
207.189.99.200/29
ASN-FLEXENTIAL blacklist 
207.189.124.0/23
ACTON-SOFTWARE blacklist 
204.156.176.0/23
ACTON-SOFTWARE blacklist 
204.156.178.0/24
- blacklist 
209.222.65.0/24
ACTON-SOFTWARE blacklist 
209.222.66.0/23
ACTON-SOFTWARE blacklist 
209.162.194.0/24
DF-PTL2-3 blacklist 
216.41.143.0/24
ACTON-SOFTWARE blacklist 
54.194.14.170 AMAZON-02 blacklist 
54.93.34.201 AMAZON-02 blacklist 
35.183.73.63 AMAZON-02 blacklist 
167.89.7.206 SENDGRID blacklist 
192.254.121.45 SENDGRID blacklist 
103.151.192.0/23
AMAZON-02 blacklist 
185.12.80.0/22
- blacklist 
188.172.128.0/20
- blacklist 
192.161.144.0/20
- blacklist 
216.198.0.0/18
AMAZON-02 blacklist 
208.86.168.7 ULTISOFTASN blacklist 
135.84.68.123 USG-PROD-WEST01 blacklist 
206.152.14.54 USG-TOR-AS blacklist 
135.84.79.54 USG-TOR-AS blacklist 
198.245.81.0/24
SALESFORCE blacklist 
136.147.176.0/24
SALESFORCE blacklist 
13.111.0.0/16
SALESFORCE blacklist 
136.147.182.0/24
SALESFORCE blacklist 
136.147.135.0/24
SALESFORCE blacklist 
199.122.123.0/24
SALESFORCE blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: jstor.org

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the registered mail servers allowed to send e-mails?

The mechanism 'mx' was set in the SPF entry. The following hosts are allowed to send

smtp2.ithaka.org
smtp1.ithaka.org
mx1.hc5909-85.iphmx.com
mx1.hc5909-85.iphmx.com
mx2.hc5909-85.iphmx.com
mx2.hc5909-85.iphmx.com

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.act-on.net
v=spf1 include:_netblocks.act-on.net -all
include:_netblocks.act-on.net
v=spf1 ip4:72.46.76.0/22 ip4:207.189.99.200/29 ip4:207.189.124.0/23 ip4:204.156.176.0/23 ip4:204.156.178.0/24 ip4:209.222.65.0/24 ip4:209.222.66.0/23 ip4:209.162.194.0/24 ip4:216.41.143.0/24 ip4:54.194.14.170 ip4:54.93.34.201 ip4:35.183.73.63 -all
ipv4:
72.46.76.0/22
ipv4:
207.189.99.200/29
ipv4:
207.189.124.0/23
ipv4:
204.156.176.0/23
ipv4:
204.156.178.0/24
ipv4:
209.222.65.0/24
ipv4:
209.222.66.0/23
ipv4:
209.162.194.0/24
ipv4:
216.41.143.0/24
ipv4:
54.194.14.170
ipv4:
54.93.34.201
ipv4:
35.183.73.63
include:u1397501.wl.sendgrid.net
v=spf1 ip4:167.89.7.206 ip4:192.254.121.45 -all
ipv4:
167.89.7.206
ipv4:
192.254.121.45
include:mail.zendesk.com
v=spf1 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ~all
ipv4:
103.151.192.0/23
ipv4:
185.12.80.0/22
ipv4:
188.172.128.0/20
ipv4:
192.161.144.0/20
ipv4:
216.198.0.0/18
include:_spf.ultipro.com
v=spf1 ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 ip4:135.84.79.54 -all
ipv4:
208.86.168.7
ipv4:
135.84.68.123
ipv4:
206.152.14.54
ipv4:
135.84.79.54
include:aspmx.pardot.com
v=spf1 include:et._spf.pardot.com -all
include:et._spf.pardot.com
v=spf1 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/16 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.0/24 -all
ipv4:
198.245.81.0/24
ipv4:
136.147.176.0/24
ipv4:
13.111.0.0/16
ipv4:
136.147.182.0/24
ipv4:
136.147.135.0/24
ipv4:
199.122.123.0/24

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 )

%{i}.spf.hc5909-85.iphmx.com

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.

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 IPv4 addresses

No explicit IPv4 addresses in the SPF record have been authorised to send

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

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:

151.101.192.152

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