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

The SPF record analysis was performed on 15.11.2024 at 02:17:17 clock.

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

Nameserverset:
a1-90.akam.net
a3-67.akam.net
a14-64.akam.net
a28-66.akam.net
a13-67.akam.net
a18-65.akam.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
52.101.41.3 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.10.18 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.10.1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.9.14 MICROSOFT-CORP-MSN-AS-BLOCK 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 
198.167.248.101 HRBL-SLC-INTERNET-BGP blacklist 
198.167.248.102 HRBL-SLC-INTERNET-BGP blacklist 
216.85.174.74 HRBL-WS-INTERNET-BGP blacklist 
216.85.174.75 HRBL-WS-INTERNET-BGP blacklist 
208.40.197.95 EXPEDIENT blacklist 
129.146.141.125 ORACLE-BMC-31898 blacklist 
129.213.108.188/32
ORACLE-BMC-31898 blacklist 
129.213.52.209/32
ORACLE-BMC-31898 blacklist 
211.154.164.170 China Networks Inter-Exchange blacklist 
211.154.164.252 China Networks Inter-Exchange blacklist 
211.154.164.180 China Networks Inter-Exchange blacklist 
211.154.164.181 China Networks Inter-Exchange blacklist 
223.255.236.217 HERBALIFESHANGHAIMANAGEMENT CO.,LTD. blacklist 
223.255.236.219 HERBALIFESHANGHAIMANAGEMENT CO.,LTD. blacklist 
122.192.50.245 CHINA UNICOM China169 Backbone blacklist 
122.192.50.247 CHINA UNICOM China169 Backbone blacklist 
64.70.67.80 CENTURYLINK-LEGACY-SAVVIS blacklist 
35.80.141.6 AMAZON-02 blacklist 
202.61.103.100 8F, Tower 2 blacklist 
194.29.73.151 Herbalife International Luxembourg S.a.R.L blacklist 
198.167.248.60 HRBL-SLC-INTERNET-BGP blacklist 
216.85.174.160 HRBL-WS-INTERNET-BGP blacklist 
192.250.28.65 DESCARTES blacklist 
198.167.248.28 HRBL-SLC-INTERNET-BGP 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 
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 
206.55.144.0/20
AMAZON-02 blacklist 
23.21.109.197 AMAZON-AES blacklist 
23.21.109.212 AMAZON-AES blacklist 
147.160.167.14 AMAZON-AES blacklist 
147.160.167.15 AMAZON-AES blacklist 
52.49.235.189 AMAZON-02 blacklist 
52.49.201.246 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: herbalife.com

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

herbalife-com.mail.protection.outlook.com
herbalife-com.mail.protection.outlook.com
herbalife-com.mail.protection.outlook.com
herbalife-com.mail.protection.outlook.com

Additional external SPF records

We could find other records authorized in the SPF record

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-a.herbalife.com
v=spf1 ip4:198.167.248.101 ip4:198.167.248.102 ip4:216.85.174.74 ip4:216.85.174.75 ip4:208.40.197.95 ip4:129.146.141.125 ip4:129.213.108.188/32 ip4:129.213.52.209/32 ip4:211.154.164.170 ip4:211.154.164.252 ip4:211.154.164.180 ip4:211.154.164.181 ~all
ipv4:
198.167.248.101
ipv4:
198.167.248.102
ipv4:
216.85.174.74
ipv4:
216.85.174.75
ipv4:
208.40.197.95
ipv4:
129.146.141.125
ipv4:
129.213.108.188/32
ipv4:
129.213.52.209/32
ipv4:
211.154.164.170
ipv4:
211.154.164.252
ipv4:
211.154.164.180
ipv4:
211.154.164.181
include:_spf-b.herbalife.com
v=spf1 ip4:223.255.236.217 ip4:223.255.236.219 ip4:122.192.50.245 ip4:122.192.50.247 ip4:64.70.67.80 ip4:35.80.141.6 ~all
ipv4:
223.255.236.217
ipv4:
223.255.236.219
ipv4:
122.192.50.245
ipv4:
122.192.50.247
ipv4:
64.70.67.80
ipv4:
35.80.141.6
include:_spf-c.herbalife.com
v=spf1 ip4:202.61.103.100 ip4:194.29.73.151 ip4:198.167.248.60 ip4:216.85.174.160 ip4:192.250.28.65 ip4:198.167.248.28 ~all
ipv4:
202.61.103.100
ipv4:
194.29.73.151
ipv4:
198.167.248.60
ipv4:
216.85.174.160
ipv4:
192.250.28.65
ipv4:
198.167.248.28
include:_spf.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
include:amazonses.com
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/19 ip4:54.240.96.0/19 ip4:76.223.128.0/19 ip4:216.221.160.0/19 ip4:206.55.144.0/20 -all
ipv4:
199.255.192.0/22
ipv4:
199.127.232.0/22
ipv4:
54.240.0.0/18
ipv4:
69.169.224.0/20
ipv4:
23.249.208.0/20
ipv4:
23.251.224.0/19
ipv4:
76.223.176.0/20
ipv4:
54.240.64.0/19
ipv4:
54.240.96.0/19
ipv4:
76.223.128.0/19
ipv4:
216.221.160.0/19
ipv4:
206.55.144.0/20
include:_spf.psm.knowbe4.com
v=spf1 ip4:23.21.109.197 ip4:23.21.109.212 ip4:147.160.167.14 ip4:147.160.167.15 ip4:52.49.235.189 ip4:52.49.201.246 -all
ipv4:
23.21.109.197
ipv4:
23.21.109.212
ipv4:
147.160.167.14
ipv4:
147.160.167.15
ipv4:
52.49.235.189
ipv4:
52.49.201.246

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

-all
Fail (non-compliant e-mails are rejected)

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

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:

a92-122-104-136.deploy.static.akamaitechnologies.com

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