SPF Check:
publicstorage.com

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 publicstorage.com.
The SPF record for publicstorage.com 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, 62 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 18.11.2024 at 00:49:32 clock.

Lookup for the domain:
publicstorage.com
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 publicstorage.com 

Nameserverset:
derek.ns.cloudflare.com
abby.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
104.18.42.21 - CLOUDFLARENET blacklist 
172.64.145.235 - CLOUDFLARENET blacklist 
148.163.149.12 PROOFPOINT-ASN-US-WEST blacklist 
148.163.149.12 PROOFPOINT-ASN-US-WEST blacklist 
206.72.127.0/24
- blacklist 
184.168.221.58 AS-26496-GO-DADDY-COM-LLC blacklist 
171.143.75.134 - blacklist 
192.237.147.88 RACKSPACE blacklist 
64.70.8.171 CENTURYLINK-LEGACY-SAVVIS blacklist 
103.28.42.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
27.126.146.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
146.88.28.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
163.47.180.0/22
AMAZON-AES blacklist 
203.55.21.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
204.75.142.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
167.89.47.10 SENDGRID blacklist 
167.89.34.30 SENDGRID blacklist 
149.72.112.51 SENDGRID blacklist 
149.72.112.52 SENDGRID blacklist 
167.89.66.219 SENDGRID blacklist 
208.117.52.163 SENDGRID blacklist 
50.31.33.140 SENDGRID blacklist 
50.31.33.141 SENDGRID blacklist 
74.63.202.239 LIMESTONENETWORKS blacklist 
149.72.240.21 SENDGRID blacklist 
149.72.163.18 SENDGRID blacklist 
168.245.55.252 SENDGRID blacklist 
3.223.8.0 AMAZON-AES blacklist 
3.208.74.172 AMAZON-AES blacklist 
52.23.113.139 AMAZON-AES blacklist 
35.168.82.240 AMAZON-AES blacklist 
149.72.142.131 SENDGRID blacklist 
54.208.86.47 AMAZON-AES blacklist 
54.177.118.13 AMAZON-02 blacklist 
52.55.39.176 AMAZON-AES blacklist 
13.57.137.3 AMAZON-02 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 
34.105.97.52 GOOGLE-CLOUD-PLATFORM blacklist 
34.74.92.186 GOOGLE-CLOUD-PLATFORM blacklist 
34.89.171.151 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.134.143 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.145.140 GOOGLE-CLOUD-PLATFORM blacklist 
35.198.110.229 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.40.234 GOOGLE-CLOUD-PLATFORM blacklist 
34.159.131.87 GOOGLE-CLOUD-PLATFORM blacklist 
34.34.77.208 GOOGLE-CLOUD-PLATFORM blacklist 
34.105.64.154 GOOGLE-CLOUD-PLATFORM blacklist 
34.75.4.19 GOOGLE-CLOUD-PLATFORM blacklist 
35.246.159.116 GOOGLE-CLOUD-PLATFORM blacklist 
34.127.10.170 GOOGLE-CLOUD-PLATFORM blacklist 
148.163.149.12 PROOFPOINT-ASN-US-WEST blacklist 
148.163.152.236 PROOFPOINT-ASN-US-EAST blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: publicstorage.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

104.18.42.21
172.64.145.235

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

mxa-0085b203.gslb.pphosted.com
mxb-0085b203.gslb.pphosted.com

Additionally authorized IPv4 addresses

Explicit IPv4 addresses in the SPF record have been authorized to send

206.72.127.0/24
184.168.221.58
171.143.75.134
192.237.147.88
64.70.8.171

Additional external SPF records

We could find other records authorized in the SPF record

include:cmail1.com
v=spf1 ip4:103.28.42.0/24 ip4:27.126.146.0/24 ip4:146.88.28.0/24 ip4:163.47.180.0/22 ip4:203.55.21.0/24 ip4:204.75.142.0/24 ~all
ipv4:
103.28.42.0/24
ipv4:
27.126.146.0/24
ipv4:
146.88.28.0/24
ipv4:
163.47.180.0/22
ipv4:
203.55.21.0/24
ipv4:
204.75.142.0/24
include:trustpilotservice.com
v=spf1 ip4:167.89.47.10 ip4:167.89.34.30 ip4:149.72.112.51 ip4:149.72.112.52 ip4:167.89.66.219 ip4:208.117.52.163 ip4:50.31.33.140 ip4:50.31.33.141 ip4:74.63.202.239 -all
ipv4:
167.89.47.10
ipv4:
167.89.34.30
ipv4:
149.72.112.51
ipv4:
149.72.112.52
ipv4:
167.89.66.219
ipv4:
208.117.52.163
ipv4:
50.31.33.140
ipv4:
50.31.33.141
ipv4:
74.63.202.239
include:_spf.q4press.com
v=spf1 a:web.q4press.com -all
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
include:_spf.axxerion.com
v=spf1 ip4:34.105.97.52 ip4:34.74.92.186 ip4:34.89.171.151 ip4:34.90.134.143 ip4:34.90.145.140 ip4:35.198.110.229 ip4:34.90.40.234 ip4:34.159.131.87 ip4:34.34.77.208 ip4:34.105.64.154 ip4:34.75.4.19 ip4:35.246.159.116 ip4:34.127.10.170 ~all
ipv4:
34.105.97.52
ipv4:
34.74.92.186
ipv4:
34.89.171.151
ipv4:
34.90.134.143
ipv4:
34.90.145.140
ipv4:
35.198.110.229
ipv4:
34.90.40.234
ipv4:
34.159.131.87
ipv4:
34.34.77.208
ipv4:
34.105.64.154
ipv4:
34.75.4.19
ipv4:
35.246.159.116
ipv4:
34.127.10.170
include:spf-0085b203.pphosted.com
v=spf1 ip4:148.163.149.12 ip4:148.163.152.236
ipv4:
148.163.149.12
ipv4:
148.163.152.236

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

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 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:

172.64.145.235

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