SPF Check:
wearegroup.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 wearegroup.com.
The SPF record for wearegroup.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 24.12.2024 at 15:12:30 clock.

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

Nameserverset:
ns-15-b.gandi.net
ns-84-a.gandi.net
ns-144-c.gandi.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
217.172.141.167 Nuco Technologies Ltd blacklist 
5.151.166.65 Glide Student & Residential Limited blacklist 
5.151.166.193 Glide Student & Residential Limited blacklist 
2603:1000::/24
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 
205.201.128.0/20
THEROCKETSCIENCEGROUP blacklist 
198.2.128.0/18
THEROCKETSCIENCEGROUP blacklist 
148.105.8.0/21
THEROCKETSCIENCEGROUP blacklist 
45.76.140.73 AS-VULTR blacklist 
45.77.59.21 AS-VULTR blacklist 
45.77.56.201 AS-VULTR blacklist 
88.150.154.127 Iomart Cloud Services Limited blacklist 
88.150.154.182 Iomart Cloud Services Limited blacklist 
185.189.237.244 Mailjet SAS blacklist 
45.77.58.210 AS-VULTR blacklist 
108.61.174.107 AS-VULTR blacklist 
2001:19f0:7402:947:5400:04ff:fe46:db2d AS-VULTR blacklist 
45.76.132.45 AS-VULTR blacklist 
2001:19f0:7402:efc:5400:04ff:fe46:db40 AS-VULTR blacklist 
88.150.154.126 Iomart Cloud Services Limited blacklist 
2001:19f0:7400:1334:5400:4ff:fe87:1005 AS-VULTR blacklist 
45.76.143.176 AS-VULTR blacklist 
2001:19f0:7402:1ffa:5400:04ff:fec8:b81c AS-VULTR blacklist 
66.245.195.219 AS-VULTR blacklist 
2a05:f480:3400:238f:5400:05ff:fe16:3b69 AS-VULTR blacklist 
64.176.183.154 AS-VULTR blacklist 
2a05:f480:3400:2bfb:5400:05ff:fe17:0fae AS-VULTR blacklist 
66.245.193.145 AS-VULTR blacklist 
2a05:f480:3400:21c3:5400:05ff:fe1a:a2e3 AS-VULTR blacklist 
64.176.184.242 AS-VULTR blacklist 
2a05:f480:3400:259b:5400:05ff:fe1a:aa36 AS-VULTR blacklist 
88.150.154.65 Iomart Cloud Services Limited 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.93.157.0/24
AMAZON-AES blacklist 
3.210.190.0/24
AMAZON-AES blacklist 
18.208.124.128/25
AMAZON-AES blacklist 
54.174.52.0/24
AMAZON-AES blacklist 
54.174.57.0/24
AMAZON-AES blacklist 
54.174.59.0/24
AMAZON-AES blacklist 
54.174.60.0/23
AMAZON-AES blacklist 
54.174.63.0/24
AMAZON-AES blacklist 
108.179.144.0/20
AMAZON-02 blacklist 
139.180.17.0/24
AMAZON-AES blacklist 
141.193.184.32/27
AMAZON-AES blacklist 
141.193.184.64/26
AMAZON-AES blacklist 
141.193.184.128/25
AMAZON-AES blacklist 
141.193.185.32/27
AMAZON-02 blacklist 
141.193.185.64/26
AMAZON-02 blacklist 
141.193.185.128/25
AMAZON-02 blacklist 
143.244.80.0/20
AMAZON-AES blacklist 
158.247.16.0/20
AMAZON-AES blacklist 
216.139.64.0/19
AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: wearegroup.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

217.172.141.167
5.151.166.65
5.151.166.193

Additionally authorized IPv6 addresses

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

2603:1000::/24

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:servers.mcsv.net
v=spf1 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 -all
ipv4:
205.201.128.0/20
ipv4:
198.2.128.0/18
ipv4:
148.105.8.0/21
include:spf.ssmx.net
v=spf1 ip4:45.76.140.73 ip4:45.77.59.21 ip4:45.77.56.201 ip4:88.150.154.127 ip4:88.150.154.182 ip4:185.189.237.244 ip4:45.77.58.210 ip4:108.61.174.107 ip6:2001:19f0:7402:947:5400:04ff:fe46:db2d ip4:45.76.132.45 ip6:2001:19f0:7402:efc:5400:04ff:fe46:db40 ip4:88.150.154.126 ip6:2001:19f0:7400:1334:5400:4ff:fe87:1005 ip4:45.76.143.176 ip6:2001:19f0:7402:1ffa:5400:04ff:fec8:b81c ip4:66.245.195.219 ip6:2a05:f480:3400:238f:5400:05ff:fe16:3b69 ip4:64.176.183.154 ip6:2a05:f480:3400:2bfb:5400:05ff:fe17:0fae ip4:66.245.193.145 ip6:2a05:f480:3400:21c3:5400:05ff:fe1a:a2e3 ip4:64.176.184.242 ip6:2a05:f480:3400:259b:5400:05ff:fe1a:aa36 ip4:88.150.154.65 -all
ipv4:
45.76.140.73
ipv4:
45.77.59.21
ipv4:
45.77.56.201
ipv4:
88.150.154.127
ipv4:
88.150.154.182
ipv4:
185.189.237.244
ipv4:
45.77.58.210
ipv4:
108.61.174.107
ipv4:
45.76.132.45
ipv4:
88.150.154.126
ipv4:
45.76.143.176
ipv4:
66.245.195.219
ipv4:
64.176.183.154
ipv4:
66.245.193.145
ipv4:
64.176.184.242
ipv4:
88.150.154.65
ipv6:
2001:19f0:7402:947:5400:04ff:fe46:db2d
ipv6:
2001:19f0:7402:efc:5400:04ff:fe46:db40
ipv6:
2001:19f0:7400:1334:5400:4ff:fe87:1005
ipv6:
2001:19f0:7402:1ffa:5400:04ff:fec8:b81c
ipv6:
2a05:f480:3400:238f:5400:05ff:fe16:3b69
ipv6:
2a05:f480:3400:2bfb:5400:05ff:fe17:0fae
ipv6:
2a05:f480:3400:21c3:5400:05ff:fe1a:a2e3
ipv6:
2a05:f480:3400:259b:5400:05ff:fe1a:aa36
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:_spf.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
include:20293962.spf07.hubspotemail.net
v=spf1 ip4:3.93.157.0/24 ip4:3.210.190.0/24 ip4:18.208.124.128/25 ip4:54.174.52.0/24 ip4:54.174.57.0/24 ip4:54.174.59.0/24 ip4:54.174.60.0/23 ip4:54.174.63.0/24 ip4:108.179.144.0/20 ip4:139.180.17.0/24 ip4:141.193.184.32/27 ip4:141.193.184.64/26 ip4:141.193.184.128/25 ip4:141.193.185.32/27 ip4:141.193.185.64/26 ip4:141.193.185.128/25 ip4:143.244.80.0/20 ip4:158.247.16.0/20 ip4:216.139.64.0/19 -all
ipv4:
3.93.157.0/24
ipv4:
3.210.190.0/24
ipv4:
18.208.124.128/25
ipv4:
54.174.52.0/24
ipv4:
54.174.57.0/24
ipv4:
54.174.59.0/24
ipv4:
54.174.60.0/23
ipv4:
54.174.63.0/24
ipv4:
108.179.144.0/20
ipv4:
139.180.17.0/24
ipv4:
141.193.184.32/27
ipv4:
141.193.184.64/26
ipv4:
141.193.184.128/25
ipv4:
141.193.185.32/27
ipv4:
141.193.185.64/26
ipv4:
141.193.185.128/25
ipv4:
143.244.80.0/20
ipv4:
158.247.16.0/20
ipv4:
216.139.64.0/19

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

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:

199.60.103.163

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