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

The SPF record analysis was performed on 06.02.2025 at 11:48:35 clock.

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

Nameserverset:
tony.ns.cloudflare.com
heather.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
74.217.54.250/31
INTERNAP-BLK3 blacklist 
49.255.152.93/31
Vocus Connect International Backbone blacklist 
74.121.167.29 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
74.121.167.30 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
88.205.100.160/27
HKN GmbH blacklist 
213.9.75.59 HKN GmbH blacklist 
213.9.75.60 HKN GmbH blacklist 
142.215.209.128/25
Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
209.236.109.189 ASN-FLEXENTIAL blacklist 
209.236.109.190 ASN-FLEXENTIAL blacklist 
202.58.142.250 Diligent Board Services Australia Pty Ltd blacklist 
202.58.142.251 Diligent Board Services Australia Pty Ltd blacklist 
202.58.140.250 Diligent Board Services Australia Pty Ltd blacklist 
202.58.140.251 Diligent Board Services Australia Pty Ltd blacklist 
89.187.106.61 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
89.187.106.62 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
89.21.6.61 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
89.21.6.62 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
149.97.158.154/31
Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
62.216.248.221 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
62.216.248.222 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
88.205.108.64/26
HKN GmbH 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 
50.31.37.184 SENDGRID blacklist 
167.89.38.213 SENDGRID blacklist 
167.89.33.51 SENDGRID 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 
167.89.0.0/17
SENDGRID blacklist 
208.117.48.0/20
SENDGRID blacklist 
50.31.32.0/19
SENDGRID blacklist 
198.37.144.0/20
SENDGRID blacklist 
198.21.0.0/21
SENDGRID blacklist 
192.254.112.0/20
SENDGRID blacklist 
168.245.0.0/17
SENDGRID blacklist 
149.72.0.0/16
AMAZON-AES blacklist 
159.183.0.0/16
SENDGRID blacklist 
223.165.113.0/24
SENDGRID blacklist 
223.165.115.0/24
SENDGRID blacklist 
223.165.118.0/23
SENDGRID blacklist 
223.165.120.0/23
SENDGRID blacklist 
3.139.206.90 AMAZON-02 blacklist 
18.219.54.208 AMAZON-02 blacklist 
18.189.50.166 AMAZON-02 blacklist 
18.118.53.214 AMAZON-02 blacklist 
3.141.139.175 AMAZON-02 blacklist 
3.22.88.143 AMAZON-02 blacklist 
192.40.160.0/19
- blacklist 
74.91.80.0/20
MOZGROUP-SMTP blacklist 
204.93.133.100 SERVERCENTRAL blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: gildan.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

204.93.133.100

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.boardbooks.com
v=spf1 ip4:74.217.54.250/31 ip4:49.255.152.93/31 ip4:74.121.167.29 ip4:74.121.167.30 ip4:88.205.100.160/27 ip4:213.9.75.59 ip4:213.9.75.60 ip4:142.215.209.128/25 ip4:209.236.109.189 ip4:209.236.109.190 ip4:202.58.142.250 ip4:202.58.142.251 ip4:202.58.140.250 ip4:202.58.140.251 ip4:89.187.106.61 ip4:89.187.106.62 ip4:89.21.6.61 ip4:89.21.6.62 ip4:149.97.158.154/31 ip4:62.216.248.221 ip4:62.216.248.222 ip4:88.205.108.64/26 ~all
ipv4:
74.217.54.250/31
ipv4:
49.255.152.93/31
ipv4:
74.121.167.29
ipv4:
74.121.167.30
ipv4:
88.205.100.160/27
ipv4:
213.9.75.59
ipv4:
213.9.75.60
ipv4:
142.215.209.128/25
ipv4:
209.236.109.189
ipv4:
209.236.109.190
ipv4:
202.58.142.250
ipv4:
202.58.142.251
ipv4:
202.58.140.250
ipv4:
202.58.140.251
ipv4:
89.187.106.61
ipv4:
89.187.106.62
ipv4:
89.21.6.61
ipv4:
89.21.6.62
ipv4:
149.97.158.154/31
ipv4:
62.216.248.221
ipv4:
62.216.248.222
ipv4:
88.205.108.64/26
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.emailicious.com
v=spf1 ip4:50.31.37.184 ip4:167.89.38.213 ip4:167.89.33.51 ~all
ipv4:
50.31.37.184
ipv4:
167.89.38.213
ipv4:
167.89.33.51
include:mail.zendesk.com
v=spf1 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ~all
ipv4:
103.151.192.0/23
ipv4:
185.12.80.0/22
ipv4:
188.172.128.0/20
ipv4:
192.161.144.0/20
ipv4:
216.198.0.0/18
include:sendgrid.net
v=spf1 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 include:ab.sendgrid.net ~all
ipv4:
167.89.0.0/17
ipv4:
208.117.48.0/20
ipv4:
50.31.32.0/19
ipv4:
198.37.144.0/20
ipv4:
198.21.0.0/21
ipv4:
192.254.112.0/20
ipv4:
168.245.0.0/17
ipv4:
149.72.0.0/16
ipv4:
159.183.0.0/16
include:ab.sendgrid.net
v=spf1 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ~all
ipv4:
223.165.113.0/24
ipv4:
223.165.115.0/24
ipv4:
223.165.118.0/23
ipv4:
223.165.120.0/23
include:mercurygate.net
v=spf1 ip4:3.139.206.90 ip4:18.219.54.208 ip4:18.189.50.166 ip4:18.118.53.214 ip4:3.141.139.175 ip4:3.22.88.143 include:_spf.smtp.com ~all
ipv4:
3.139.206.90
ipv4:
18.219.54.208
ipv4:
18.189.50.166
ipv4:
18.118.53.214
ipv4:
3.141.139.175
ipv4:
3.22.88.143
include:_spf.smtp.com
v=spf1 ip4:192.40.160.0/19 ip4:74.91.80.0/20 ~all
ipv4:
192.40.160.0/19
ipv4:
74.91.80.0/20

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)

Unknown mechanisms

Unknown mechanisms were found in the SPF record


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

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

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:

104.18.1.76

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.
© 2025 nicmanager.com.   All rights reserved.
nicmanager