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

The SPF record analysis was performed on 25.12.2024 at 21:30:24 clock.

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

Nameserverset:
ns100.worldnic.com
ns99.worldnic.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
207.211.31.0/25
NAVISITE-EAST-2 blacklist 
205.139.110.0/24
MIMECAST blacklist 
216.205.24.0/24
MIMECAST blacklist 
170.10.129.0/24
MIMECAST blacklist 
63.128.21.0/24
MIMECAST blacklist 
170.10.133.0/24
MIMECAST blacklist 
185.58.84.93 Mimecast Services Limited blacklist 
207.211.41.113 NAVISITE-EAST-2 blacklist 
207.211.30.64/26
MIMECAST blacklist 
207.211.30.128/25
MIMECAST blacklist 
216.145.221.0/24
AMAZON-AES blacklist 
170.10.128.0/24
MIMECAST blacklist 
170.10.132.56/29
MIMECAST blacklist 
170.10.132.64/29
MIMECAST blacklist 
209.61.151.0/24
RMH-14 blacklist 
166.78.68.0/22
RACKSPACE blacklist 
198.61.254.0/23
RACKSPACE blacklist 
192.237.158.0/23
RACKSPACE blacklist 
23.253.182.0/23
RACKSPACE blacklist 
104.130.96.0/28
RACKSPACE blacklist 
146.20.113.0/24
RACKSPACE blacklist 
146.20.191.0/24
RACKSPACE blacklist 
159.135.224.0/20
MAILGUN blacklist 
69.72.32.0/20
MAILGUN blacklist 
104.130.122.0/23
RACKSPACE blacklist 
146.20.112.0/26
RACKSPACE blacklist 
161.38.192.0/20
MAILGUN blacklist 
143.55.224.0/21
MAILGUN blacklist 
143.55.232.0/22
MAILGUN blacklist 
159.112.240.0/20
MAILGUN blacklist 
198.244.48.0/20
MAILGUN blacklist 
204.220.168.0/21
VOYANT blacklist 
204.220.176.0/20
MAILGUN blacklist 
141.193.32.0/23
AMAZON-02 blacklist 
159.135.140.80/29
Rackspace Ltd. blacklist 
159.135.132.128/25
Rackspace Ltd. blacklist 
161.38.204.0/22
AMAZON-02 blacklist 
87.253.232.0/21
Mailjet SAS blacklist 
185.189.236.0/22
Mailjet SAS blacklist 
185.211.120.0/22
Mailjet SAS blacklist 
185.250.236.0/22
Mailjet SAS blacklist 
143.55.236.0/22
Mailjet SAS blacklist 
198.244.60.0/22
Mailjet SAS 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 
207.211.30.40 MIMECAST blacklist 
207.211.30.41 MIMECAST blacklist 
207.211.30.42 MIMECAST blacklist 
207.211.30.43 MIMECAST blacklist 
207.211.30.44 MIMECAST blacklist 
207.211.30.45 MIMECAST blacklist 
207.211.30.46 MIMECAST blacklist 
207.211.30.47 MIMECAST blacklist 
207.211.30.48 MIMECAST blacklist 
207.211.30.49 MIMECAST blacklist 
205.139.111.40 MIMECAST blacklist 
205.139.111.41 MIMECAST blacklist 
205.139.111.42 MIMECAST blacklist 
205.139.111.43 MIMECAST blacklist 
205.139.111.44 MIMECAST blacklist 
205.139.111.45 MIMECAST blacklist 
205.139.111.46 MIMECAST blacklist 
205.139.111.47 MIMECAST blacklist 
205.139.111.48 MIMECAST blacklist 
205.139.111.49 MIMECAST 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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: pcs-company.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Will be forwarded to another SPF record?

There is an SPF record that refers to another SPF record Additional entries in this record are therefore ignored.

redirect:b53vyrtt._spf._d.mim.ec
v=spf1 exists:%{i}._spf.mta.salesforce.com ip4:207.211.31.0/25 ip4:205.139.110.0/24 ip4:216.205.24.0/24 ip4:170.10.129.0/24 ip4:63.128.21.0/24 ip4:170.10.133.0/24 ip4:185.58.84.93 ip4:207.211.41.113 ip4:207.211.30.64/26 ip4:207.211.30.128/25 ip4:216.145.221.0/24 ip4:170.10.128.0/24 ip4:170.10.132.56/29 ip4:170.10.132.64/29 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 include:b53vyrtt1._spf._d.mim.ec ~all
ipv4:
207.211.31.0/25
ipv4:
205.139.110.0/24
ipv4:
216.205.24.0/24
ipv4:
170.10.129.0/24
ipv4:
63.128.21.0/24
ipv4:
170.10.133.0/24
ipv4:
185.58.84.93
ipv4:
207.211.41.113
ipv4:
207.211.30.64/26
ipv4:
207.211.30.128/25
ipv4:
216.145.221.0/24
ipv4:
170.10.128.0/24
ipv4:
170.10.132.56/29
ipv4:
170.10.132.64/29
ipv4:
209.61.151.0/24
ipv4:
166.78.68.0/22
ipv4:
198.61.254.0/23
include:b53vyrtt1._spf._d.mim.ec
v=spf1 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:141.193.32.0/23 ip4:159.135.140.80/29 include:b53vyrtt2._spf._d.mim.ec ~all
ipv4:
192.237.158.0/23
ipv4:
23.253.182.0/23
ipv4:
104.130.96.0/28
ipv4:
146.20.113.0/24
ipv4:
146.20.191.0/24
ipv4:
159.135.224.0/20
ipv4:
69.72.32.0/20
ipv4:
104.130.122.0/23
ipv4:
146.20.112.0/26
ipv4:
161.38.192.0/20
ipv4:
143.55.224.0/21
ipv4:
143.55.232.0/22
ipv4:
159.112.240.0/20
ipv4:
198.244.48.0/20
ipv4:
204.220.168.0/21
ipv4:
204.220.176.0/20
ipv4:
141.193.32.0/23
ipv4:
159.135.140.80/29
include:b53vyrtt2._spf._d.mim.ec
v=spf1 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 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 ip4:207.211.30.40 ip4:207.211.30.41 ip4:207.211.30.42 ip4:207.211.30.43 ip4:207.211.30.44 ip4:207.211.30.45 include:b53vyrtt3._spf._d.mim.ec ~all
ipv4:
159.135.132.128/25
ipv4:
161.38.204.0/22
ipv4:
87.253.232.0/21
ipv4:
185.189.236.0/22
ipv4:
185.211.120.0/22
ipv4:
185.250.236.0/22
ipv4:
143.55.236.0/22
ipv4:
198.244.60.0/22
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
ipv4:
207.211.30.40
ipv4:
207.211.30.41
ipv4:
207.211.30.42
ipv4:
207.211.30.43
ipv4:
207.211.30.44
ipv4:
207.211.30.45
include:b53vyrtt3._spf._d.mim.ec
v=spf1 ip4:207.211.30.46 ip4:207.211.30.47 ip4:207.211.30.48 ip4:207.211.30.49 ip4:205.139.111.40 ip4:205.139.111.41 ip4:205.139.111.42 ip4:205.139.111.43 ip4:205.139.111.44 ip4:205.139.111.45 ip4:205.139.111.46 ip4:205.139.111.47 ip4:205.139.111.48 ip4:205.139.111.49 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 include:b53vyrtt4._spf._d.mim.ec ~all
ipv4:
207.211.30.46
ipv4:
207.211.30.47
ipv4:
207.211.30.48
ipv4:
207.211.30.49
ipv4:
205.139.111.40
ipv4:
205.139.111.41
ipv4:
205.139.111.42
ipv4:
205.139.111.43
ipv4:
205.139.111.44
ipv4:
205.139.111.45
ipv4:
205.139.111.46
ipv4:
205.139.111.47
ipv4:
205.139.111.48
ipv4:
205.139.111.49
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
include:b53vyrtt4._spf._d.mim.ec
v=spf1 ip6:2a01:111:f403:f000::/52 ~all
ipv6:
2a01:111:f403:f000::/52

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

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 )

E-Mail handling

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

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:

cloudproxy10069.sucuri.net

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