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

The SPF record analysis was performed on 05.11.2024 at 04:34:10 clock.

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

Nameserverset:
ns31.constellix.com
ns11.constellix.com
ns21.constellix.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
52.235.47.135 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
208.86.168.7 ULTISOFTASN blacklist 
135.84.68.123 USG-PROD-WEST01 blacklist 
206.152.14.54 USG-TOR-AS blacklist 
135.84.79.54 USG-TOR-AS blacklist 
35.231.189.43 GOOGLE-CLOUD-PLATFORM blacklist 
34.74.57.127 GOOGLE-CLOUD-PLATFORM blacklist 
35.231.237.213 GOOGLE-CLOUD-PLATFORM blacklist 
35.202.125.231 GOOGLE-CLOUD-PLATFORM blacklist 
35.188.64.218 GOOGLE-CLOUD-PLATFORM blacklist 
34.68.104.193 GOOGLE-CLOUD-PLATFORM blacklist 
34.75.49.213 GOOGLE-CLOUD-PLATFORM blacklist 
35.229.62.77 GOOGLE-CLOUD-PLATFORM blacklist 
34.75.16.178 GOOGLE-CLOUD-PLATFORM blacklist 
35.184.208.151 GOOGLE-CLOUD-PLATFORM blacklist 
35.203.125.236 GOOGLE-CLOUD-PLATFORM blacklist 
35.203.39.206 GOOGLE-CLOUD-PLATFORM blacklist 
35.203.101.94 GOOGLE-CLOUD-PLATFORM blacklist 
35.201.16.52 GOOGLE-CLOUD-PLATFORM blacklist 
34.151.97.101 GOOGLE-CLOUD-PLATFORM blacklist 
35.244.76.3 GOOGLE-CLOUD-PLATFORM blacklist 
35.246.204.223 GOOGLE-CLOUD-PLATFORM blacklist 
35.246.194.59 GOOGLE-CLOUD-PLATFORM blacklist 
34.89.204.64 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.168.255 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.61.249 GOOGLE-CLOUD-PLATFORM blacklist 
34.90.80.160 GOOGLE-CLOUD-PLATFORM blacklist 
174.128.53.51 IMDC-AS12025 blacklist 
174.128.53.52 IMDC-AS12025 blacklist 
174.128.53.53 IMDC-AS12025 blacklist 
38.72.70.51 KDWLLP1 blacklist 
38.72.70.52 KDWLLP1 blacklist 
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/32
Mimecast Services Limited blacklist 
207.211.41.113/32
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 
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 
52.229.64.105 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.86.247.52 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.86.225.121 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.151.230.19 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.124.2.148 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.86.217.129 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.237.30.247 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: kelleydrye.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized A-records?

In addition to the A-records stored in the DNS, we were able to find further records authorized in the SPF-record

52.235.47.135

Additionally authorized IPv4 addresses

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

174.128.53.51
174.128.53.52
174.128.53.53
38.72.70.51
38.72.70.52

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.ultipro.com
v=spf1 ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 ip4:135.84.79.54 -all
ipv4:
208.86.168.7
ipv4:
135.84.68.123
ipv4:
206.152.14.54
ipv4:
135.84.79.54
include:_spf.saashr.com
v=spf1 ip4:35.231.189.43 ip4:34.74.57.127 ip4:35.231.237.213 ip4:35.202.125.231 ip4:35.188.64.218 ip4:34.68.104.193 include:spf1.saashr.com include:spf2.saashr.com ~all
ipv4:
35.231.189.43
ipv4:
34.74.57.127
ipv4:
35.231.237.213
ipv4:
35.202.125.231
ipv4:
35.188.64.218
ipv4:
34.68.104.193
include:spf1.saashr.com
v=spf1 ip4:34.75.49.213 ip4:35.229.62.77 ip4:34.75.16.178 ip4:35.184.208.151 ip4:35.203.125.236 ip4:35.203.39.206 ip4:35.203.101.94 ip4:35.201.16.52
ipv4:
34.75.49.213
ipv4:
35.229.62.77
ipv4:
34.75.16.178
ipv4:
35.184.208.151
ipv4:
35.203.125.236
ipv4:
35.203.39.206
ipv4:
35.203.101.94
ipv4:
35.201.16.52
include:spf2.saashr.com
v=spf1 ip4:34.151.97.101 ip4:35.244.76.3 ip4:35.246.204.223 ip4:35.246.194.59 ip4:34.89.204.64 ip4:34.90.168.255 ip4:34.90.61.249 ip4:34.90.80.160
ipv4:
34.151.97.101
ipv4:
35.244.76.3
ipv4:
35.246.204.223
ipv4:
35.246.194.59
ipv4:
34.89.204.64
ipv4:
34.90.168.255
ipv4:
34.90.61.249
ipv4:
34.90.80.160
include:us._netblocks.mimecast.com
v=spf1 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/32 ip4:207.211.41.113/32 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 ~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/32
ipv4:
207.211.41.113/32
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
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-ca.emailsignatures365.com
v=spf1 ip4:52.229.64.105 ip4:40.86.247.52 ip4:40.86.225.121 ip4:20.151.230.19 ip4:40.124.2.148 ip4:40.86.217.129 ip4:52.237.30.247 -all
ipv4:
52.229.64.105
ipv4:
40.86.247.52
ipv4:
40.86.225.121
ipv4:
20.151.230.19
ipv4:
40.124.2.148
ipv4:
40.86.217.129
ipv4:
52.237.30.247

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.

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

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

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