SPF Check:
_spf-sfdc.successfactors.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
Warning: Compliance breach for email deliverability & security

The domain _spf-sfdc.successfactors.com does not fulfil the requirements for optimal deliverability to Google, Yahoo and other email service providers.

Mandatory IT baseline protection measures for email security are not fulfilled. There are risks of email misuse.

Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain _spf-sfdc.successfactors.com.
The SPF record for _spf-sfdc.successfactors.com is valid.
The syntax check of the SPF record shows no obvious errors.

Which IP-s are legitimate to send emails?
In total, 88 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 14.11.2024 at 03:56:10 clock.

Lookup for the domain:
_spf-sfdc.successfactors.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 _spf-sfdc.successfactors.com 

Nameserverset:
ns4.sap-ag.de
ns.sap-ag.de
ns3.sap-ag.de
ns5.sap.com
ns2.sap.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
35.214.208.81 GOOGLE blacklist 
35.214.213.218 GOOGLE blacklist 
35.214.183.81 GOOGLE blacklist 
35.214.212.238 GOOGLE blacklist 
130.214.213.2 SAP SE blacklist 
130.214.213.20 SAP SE blacklist 
130.214.213.6 SAP SE blacklist 
130.214.213.7 SAP SE blacklist 
130.214.222.200 SAP SE blacklist 
130.214.222.201 SAP SE blacklist 
130.214.228.203 SAP SE blacklist 
130.214.228.204 SAP SE blacklist 
130.214.250.239 SAP SE blacklist 
130.214.250.241 SAP SE blacklist 
155.56.220.141 SAP SE blacklist 
155.56.220.142 SAP SE blacklist 
155.56.221.13 SAP SE blacklist 
155.56.221.14 SAP SE blacklist 
155.56.221.15 SAP SE blacklist 
155.56.221.16 SAP SE blacklist 
155.56.222.26 SAP SE blacklist 
155.56.222.27 SAP SE blacklist 
157.133.1.19 - blacklist 
157.133.1.20 - blacklist 
157.133.165.105 SAP ASIA PTE LTD blacklist 
157.133.165.106 SAP ASIA PTE LTD blacklist 
157.133.169.10 SAP SE blacklist 
157.133.169.11 SAP SE blacklist 
157.133.241.19 - blacklist 
157.133.241.20 - blacklist 
157.133.48.19 SAP-DC-TO blacklist 
157.133.48.20 SAP-DC-TO blacklist 
20.36.220.122 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.42.38.64 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
210.80.140.141 UUNET blacklist 
210.80.140.142 UUNET blacklist 
213.52.186.141 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
213.52.186.142 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
34.107.8.58 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.200.156 GOOGLE-CLOUD-PLATFORM blacklist 
34.98.25.137 GOOGLE-CLOUD-PLATFORM blacklist 
34.98.33.16 GOOGLE-CLOUD-PLATFORM blacklist 
35.194.96.54 GOOGLE-CLOUD-PLATFORM blacklist 
35.204.47.209 GOOGLE-CLOUD-PLATFORM blacklist 
35.234.108.85 GOOGLE-CLOUD-PLATFORM blacklist 
35.242.247.107 GOOGLE-CLOUD-PLATFORM blacklist 
35.243.100.38 GOOGLE-CLOUD-PLATFORM blacklist 
40.67.152.191 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.80.240.102 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.80.240.122 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.91.116.129 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.91.81.213 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.139.16.8 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.139.2.137 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.151.239.159 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.188.137.143 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.188.137.23 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.228.105.245 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.228.106.137 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
65.221.12.128 UUNET blacklist 
65.221.12.148 UUNET blacklist 
65.221.8.29 UUNET blacklist 
70.42.227.151 ASN-INTERNAP-BLK blacklist 
70.42.227.152 ASN-INTERNAP-BLK blacklist 
70.42.227.180 ASN-INTERNAP-BLK blacklist 
70.42.227.181 ASN-INTERNAP-BLK blacklist 
130.214.193.83 SAP SE blacklist 
130.214.193.93 SAP SE blacklist 
130.214.193.78 SAP SE blacklist 
130.214.193.85 SAP SE blacklist 
130.214.156.205 SAP SE blacklist 
130.214.156.249 SAP SE blacklist 
20.114.134.190 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.122.10.46 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.250.50.60 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.250.57.206 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.250.50.60 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.250.57.206 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.107.232.86 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.107.225.153 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.1.128.197 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.10.24.226 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.96.12.43 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.1.130.13 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.119.174.191 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.114.186.35 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.230.106.230 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.119.207.133 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: _spf-sfdc.successfactors.com

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

35.214.208.81
35.214.213.218
35.214.183.81
35.214.212.238
130.214.213.2
130.214.213.20
130.214.213.6
130.214.213.7
130.214.222.200
130.214.222.201
130.214.228.203
130.214.228.204
130.214.250.239
130.214.250.241
155.56.220.141
155.56.220.142
155.56.221.13
155.56.221.14
155.56.221.15
155.56.221.16
155.56.222.26
155.56.222.27
157.133.1.19
157.133.1.20
157.133.165.105
157.133.165.106
157.133.169.10
157.133.169.11
157.133.241.19
157.133.241.20
157.133.48.19
157.133.48.20
20.36.220.122
20.42.38.64
210.80.140.141
210.80.140.142
213.52.186.141
213.52.186.142
34.107.8.58
34.90.200.156
34.98.25.137
34.98.33.16
35.194.96.54
35.204.47.209
35.234.108.85
35.242.247.107
35.243.100.38
40.67.152.191
40.80.240.102
40.80.240.122
40.91.116.129
40.91.81.213
52.139.16.8
52.139.2.137
52.151.239.159
52.188.137.143
52.188.137.23
52.228.105.245
52.228.106.137
65.221.12.128
65.221.12.148
65.221.8.29
70.42.227.151
70.42.227.152
70.42.227.180
70.42.227.181
130.214.193.83
130.214.193.93
130.214.193.78
130.214.193.85
130.214.156.205
130.214.156.249
20.114.134.190
20.122.10.46
20.250.50.60
20.250.57.206
20.250.50.60
20.250.57.206
51.107.232.86
51.107.225.153
20.1.128.197
20.10.24.226
20.96.12.43
20.1.130.13
20.119.174.191
20.114.186.35
20.230.106.230
20.119.207.133

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.

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

Additional external SPF records

We could not find any other records authorized in SPF-Record

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