Solve your problems in no time
Guaranteed measurable improvement for email deliverability and domain security
Solve your problems in no time
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.
Does a valid SPF record exist?
An SPF record was found for the domain zenoss.com.
The SPF record for zenoss.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, 83 IP address(es) were authorized by the SPF record to send emails.
The SPF record analysis was performed on 16.04.2024 at 15:31:32 clock.
| IP | Provider / ASN | DNSBL-Check | ||
|---|---|---|---|---|
| 142.250.153.27 | blacklist | |||
| 2a00:1450:4013:c16:0:0:0:1a | blacklist | |||
| 142.250.153.27 | blacklist | |||
| 2a00:1450:4013:c16:0:0:0:1b | blacklist | |||
| 142.251.9.26 | blacklist | |||
| 2a00:1450:4025:c03:0:0:0:1a | blacklist | |||
| 64.233.166.26 | blacklist | |||
| 2a00:1450:400c:c1d:0:0:0:1b | blacklist | |||
| 142.251.9.27 | blacklist | |||
| 2a00:1450:4025:c03:0:0:0:1b | blacklist | |||
| 35.190.247.0/24
|
GOOGLE-CLOUD-PLATFORM | blacklist | ||
| 64.233.160.0/19
|
blacklist | |||
| 66.102.0.0/20
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
blacklist | |||
| 35.191.0.0/16
|
blacklist | |||
| 130.211.0.0/22
|
GOOGLE-CLOUD-PLATFORM | 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 | ||
| 35.161.50.59 | AMAZON-02 | blacklist | ||
| 13.110.78.181 | SALESFORCE | blacklist | ||
| 13.110.78.0/24
|
SALESFORCE | blacklist | ||
| 13.53.158.74 | AMAZON-02 | blacklist | ||
| 54.208.81.130 | AMAZON-AES | blacklist | ||
| 130.110.74.0/24
|
- | blacklist | ||
| 23.21.109.212 | AMAZON-AES | blacklist | ||
| 23.21.109.197 | AMAZON-AES | blacklist | ||
| 52.49.201.246 | AMAZON-02 | blacklist | ||
| 52.49.235.189 | AMAZON-02 | blacklist | ||
| 54.172.84.90 | AMAZON-AES | blacklist | ||
| 147.160.167.0/24
|
AMAZON-AES | blacklist | ||
| 199.255.192.0/22
|
AMAZON-02 | blacklist | ||
| 199.127.232.0/22
|
AMAZON-02 | blacklist | ||
| 54.240.0.0/18
|
AMAZON-02 | blacklist | ||
| 69.169.224.0/20
|
AMAZON-02 | blacklist | ||
| 23.249.208.0/20
|
AMAZON-02 | blacklist | ||
| 23.251.224.0/19
|
AMAZON-02 | blacklist | ||
| 76.223.176.0/20
|
AMAZON-02 | blacklist | ||
| 52.82.172.0/22
|
Ningxia West Cloud Data Technology Co.Ltd. | blacklist | ||
| 54.240.64.0/19
|
AMAZON-AES | blacklist | ||
| 54.240.96.0/19
|
AMAZON-02 | blacklist | ||
| 76.223.128.0/19
|
AMAZON-02 | blacklist | ||
| 216.221.160.0/19
|
AMAZON-02 | blacklist | ||
| 199.15.212.0/22
|
OMNITURE | blacklist | ||
| 72.3.185.0/24
|
RMH-14 | blacklist | ||
| 72.32.154.0/24
|
RMH-14 | blacklist | ||
| 72.32.217.0/24
|
RMH-14 | blacklist | ||
| 72.32.243.0/24
|
RMH-14 | blacklist | ||
| 94.236.119.0/26
|
Rackspace Ltd. | blacklist | ||
| 37.188.97.188/32
|
Rackspace Ltd. | blacklist | ||
| 185.28.196.0/22
|
Rackspace Ltd. | blacklist | ||
| 192.28.128.0/18
|
LM-CORP | blacklist | ||
| 103.237.104.0/22
|
MARKETO | blacklist | ||
| 130.248.172.0/24
|
OMNITURE | blacklist | ||
| 130.248.173.0/24
|
OMNITURE | blacklist | ||
| 54.208.138.239 | AMAZON-AES | blacklist | ||
| 173.203.82.6 | RACKSPACE | blacklist | ||
| 192.254.121.248 | SENDGRID | blacklist | ||
| 66.40.36.104 | COGECO-PEER1 | blacklist | ||
| 52.62.89.36 | AMAZON-02 | blacklist |
|
(zenoss.com → _phishspf.knowbe4.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '23.21.109.212'
OK for 'ip4' -> '23.21.109.197'
OK for 'ip4' -> '52.49.201.246'
OK for 'ip4' -> '52.49.235.189'
OK for 'ip4' -> '54.172.84.90'
OK for 'ip4' -> '147.160.167.0/24'
OK for 'all' -> '-'
|
|
(zenoss.com → _spf.zenoss.com) The SPF consists of a permissible character set.
The SPF record of _spf.zenoss.com contains valid characters.
|
|
(zenoss.com) The DNS lookup limit was not exceeded.
The limit was not exceeded:
1: zenoss.com - MX 2: zenoss.com include:_spf.google.com 3: zenoss.com include:_spf.google.com include:_netblocks.google.com 4: zenoss.com include:_spf.google.com include:_netblocks2.google.com 5: zenoss.com include:_spf.google.com include:_netblocks3.google.com 6: zenoss.com include:mail.zendesk.com 7: zenoss.com include:_spf.zenoss.com 8: zenoss.com include:_phishspf.knowbe4.com 9: zenoss.com include:amazonses.com 10: zenoss.com include:mktomail.com |
|
(zenoss.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'include' -> 'mail.zendesk.com'
OK for 'ip4' -> '52.62.89.36'
OK for 'ip4' -> '66.40.36.104'
OK for 'ip4' -> '192.254.121.248'
OK for 'ip4' -> '173.203.82.6'
OK for 'ip4' -> '54.208.138.239'
OK for 'include' -> 'mktomail.com'
OK for 'include' -> 'amazonses.com'
OK for 'include' -> '_phishspf.knowbe4.com'
OK for 'include' -> '_spf.zenoss.com'
OK for 'include' -> '_spf.google.com'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'mx'
OK for 'all' -> '~'
|
|
(zenoss.com → mktomail.com) The SPF consists of a permissible character set.
The SPF record of mktomail.com contains valid characters.
|
|
(zenoss.com → mktomail.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '199.15.212.0/22'
OK for 'ip4' -> '72.3.185.0/24'
OK for 'ip4' -> '72.32.154.0/24'
OK for 'ip4' -> '72.32.217.0/24'
OK for 'ip4' -> '72.32.243.0/24'
OK for 'ip4' -> '94.236.119.0/26'
OK for 'ip4' -> '37.188.97.188/32'
OK for 'ip4' -> '185.28.196.0/22'
OK for 'ip4' -> '192.28.128.0/18'
OK for 'ip4' -> '103.237.104.0/22'
OK for 'ip4' -> '130.248.172.0/24'
OK for 'ip4' -> '130.248.173.0/24'
OK for 'all' -> '~'
|
|
(zenoss.com → mail.zendesk.com) The SPF consists of a permissible character set.
The SPF record of mail.zendesk.com contains valid characters.
|
|
(zenoss.com → mail.zendesk.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '103.151.192.0/23'
OK for 'ip4' -> '185.12.80.0/22'
OK for 'ip4' -> '188.172.128.0/20'
OK for 'ip4' -> '192.161.144.0/20'
OK for 'ip4' -> '216.198.0.0/18'
OK for 'all' -> '~'
|
|
(zenoss.com → amazonses.com) The SPF consists of a permissible character set.
The SPF record of amazonses.com contains valid characters.
|
|
(zenoss.com → amazonses.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '199.255.192.0/22'
OK for 'ip4' -> '199.127.232.0/22'
OK for 'ip4' -> '54.240.0.0/18'
OK for 'ip4' -> '69.169.224.0/20'
OK for 'ip4' -> '23.249.208.0/20'
OK for 'ip4' -> '23.251.224.0/19'
OK for 'ip4' -> '76.223.176.0/20'
OK for 'ip4' -> '52.82.172.0/22'
OK for 'ip4' -> '54.240.64.0/19'
OK for 'ip4' -> '54.240.96.0/19'
OK for 'ip4' -> '76.223.128.0/19'
OK for 'ip4' -> '216.221.160.0/19'
OK for 'all' -> '-'
|
|
(zenoss.com → _spf.zenoss.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '35.161.50.59'
OK for 'ip4' -> '13.110.78.181'
OK for 'ip4' -> '13.110.78.0/24'
OK for 'ip4' -> '13.53.158.74'
OK for 'ip4' -> '54.208.81.130'
OK for 'ip4' -> '130.110.74.0/24'
OK for 'all' -> '~'
|
|
(zenoss.com → _phishspf.knowbe4.com) The SPF consists of a permissible character set.
The SPF record of _phishspf.knowbe4.com contains valid characters.
|
|
(zenoss.com → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(zenoss.com → _spf.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'include' -> '_netblocks.google.com'
OK for 'include' -> '_netblocks2.google.com'
OK for 'include' -> '_netblocks3.google.com'
OK for 'all' -> '~'
|
|
(zenoss.com → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(zenoss.com → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'ip4' -> '35.191.0.0/16'
OK for 'ip4' -> '130.211.0.0/22'
OK for 'all' -> '~'
|
|
(zenoss.com → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(zenoss.com → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(zenoss.com → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(zenoss.com → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '35.190.247.0/24'
OK for 'ip4' -> '64.233.160.0/19'
OK for 'ip4' -> '66.102.0.0/20'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
|
(zenoss.com) The SPF consists of a permissible character set.
The SPF record of zenoss.com contains valid characters.
|
SPF record available?
We found an SPF record for the domain.
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
Additionally authorized IPv4 addresses
Explicit IPv4 addresses in the SPF record have been authorized to send
Additional external SPF records
We could find other records authorized in the SPF record
E-Mail handling
How should the checkHost() function of the e-mail server handle the e-mail? (syntax )
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 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.
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:
119.142.111.34.bc.googleusercontent.com
Get a first impression of the risk potential in your company
