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

The SPF record analysis was performed on 27.12.2024 at 05:05:30 clock.

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

Nameserverset:
ns-818.awsdns-38.net
ns-288.awsdns-36.com
ns-2021.awsdns-60.co.uk
ns-1468.awsdns-55.org
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
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 
54.165.188.221 AMAZON-AES blacklist 
54.165.188.221 AMAZON-AES blacklist 
54.165.188.221 AMAZON-AES blacklist 
52.73.19.250 AMAZON-AES blacklist 
54.165.188.221 AMAZON-AES blacklist 
52.5.61.5 AMAZON-AES blacklist 
199.15.212.0/22
OMNITURE blacklist 
72.3.185.0/24
RMH-14 blacklist 
72.32.154.0/24
RMH-14 blacklist 
72.32.217.0/24
RMH-14 blacklist 
72.32.243.0/24
RMH-14 blacklist 
94.236.119.0/26
Rackspace Ltd. blacklist 
37.188.97.188/32
Rackspace Ltd. blacklist 
185.28.196.0/22
Rackspace Ltd. blacklist 
192.28.128.0/18
LM-CORP blacklist 
103.237.104.0/22
MARKETO blacklist 
130.248.172.0/24
OMNITURE blacklist 
130.248.173.0/24
OMNITURE blacklist 
52.31.132.175 AMAZON-02 blacklist 
52.19.188.226 AMAZON-02 blacklist 
66.119.37.184/30
CENTURYLINK-LEGACY-SAVVIS blacklist 
66.119.37.167 CENTURYLINK-LEGACY-SAVVIS blacklist 
69.42.126.188 UUNET blacklist 
54.187.222.61 AMAZON-02 blacklist 
52.24.154.46 AMAZON-02 blacklist 
52.33.16.1 AMAZON-02 blacklist 
54.69.62.181 AMAZON-02 blacklist 
34.208.255.239 AMAZON-02 blacklist 
13.58.82.59 AMAZON-02 blacklist 
52.14.134.251 AMAZON-02 blacklist 
52.14.208.59 AMAZON-02 blacklist 
13.58.57.211 AMAZON-02 blacklist 
13.58.126.18 AMAZON-02 blacklist 
52.14.179.237 AMAZON-02 blacklist 
13.58.98.241 AMAZON-02 blacklist 
52.14.175.191 AMAZON-02 blacklist 
52.15.213.186 AMAZON-02 blacklist 
13.58.86.183 AMAZON-02 blacklist 
34.209.181.84 AMAZON-02 blacklist 
35.161.82.137 AMAZON-02 blacklist 
52.14.70.114 AMAZON-02 blacklist 
52.15.230.220 AMAZON-02 blacklist 
52.15.208.139 AMAZON-02 blacklist 
52.15.62.153 AMAZON-02 blacklist 
13.58.58.6 AMAZON-02 blacklist 
54.71.252.65 AMAZON-02 blacklist 
52.28.49.94 AMAZON-02 blacklist 
52.29.41.175 AMAZON-02 blacklist 
52.29.197.69 AMAZON-02 blacklist 
52.48.124.108 AMAZON-02 blacklist 
54.240.60.174/31
AMAZON-02 blacklist 
35.160.0.242 AMAZON-02 blacklist 
34.213.36.118 AMAZON-02 blacklist 
185.132.37.57 IONOS SE blacklist 
213.171.215.79 IONOS SE blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: saemediagroup.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

185.132.37.57
213.171.215.79

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:contest.techbriefs.com
v=spf1 mx a a:createthefuturecontest.com ip4:52.73.19.250 ip4:54.165.188.221 ip4:52.5.61.5 -all
a:
54.165.188.221
mx:
contest.techbriefs.com
ipv4:
52.73.19.250
ipv4:
54.165.188.221
ipv4:
52.5.61.5
include:mktomail.com
v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip4:130.248.172.0/24 ip4:130.248.173.0/24 ~all
ipv4:
199.15.212.0/22
ipv4:
72.3.185.0/24
ipv4:
72.32.154.0/24
ipv4:
72.32.217.0/24
ipv4:
72.32.243.0/24
ipv4:
94.236.119.0/26
ipv4:
37.188.97.188/32
ipv4:
185.28.196.0/22
ipv4:
192.28.128.0/18
ipv4:
103.237.104.0/22
ipv4:
130.248.172.0/24
ipv4:
130.248.173.0/24
include:spf.workfront.com
v=spf1 ip4:52.31.132.175 ip4:52.19.188.226 ip4:66.119.37.184/30 ip4:66.119.37.167 ip4:69.42.126.188 ip4:54.187.222.61 ip4:52.24.154.46 ip4:52.33.16.1 ip4:54.69.62.181 ip4:34.208.255.239 ip4:13.58.82.59 ip4:52.14.134.251 ip4:52.14.208.59 ip4:13.58.57.211 ip4:13.58.126.18 ip4:52.14.179.237 ip4:13.58.98.241 ip4:52.14.175.191 ip4:52.15.213.186 ip4:13.58.86.183 ip4:34.209.181.84 ip4:35.161.82.137 ip4:52.14.70.114 ip4:52.15.230.220 ip4:52.15.208.139 ip4:52.15.62.153 ip4:13.58.58.6 ip4:54.71.252.65 ip4:52.28.49.94 ip4:52.29.41.175 ip4:52.29.197.69 ip4:52.48.124.108 ip4:54.240.60.174/31 ip4:35.160.0.242 ip4:34.213.36.118 -all
ipv4:
52.31.132.175
ipv4:
52.19.188.226
ipv4:
66.119.37.184/30
ipv4:
66.119.37.167
ipv4:
69.42.126.188
ipv4:
54.187.222.61
ipv4:
52.24.154.46
ipv4:
52.33.16.1
ipv4:
54.69.62.181
ipv4:
34.208.255.239
ipv4:
13.58.82.59
ipv4:
52.14.134.251
ipv4:
52.14.208.59
ipv4:
13.58.57.211
ipv4:
13.58.126.18
ipv4:
52.14.179.237
ipv4:
13.58.98.241
ipv4:
52.14.175.191
ipv4:
52.15.213.186
ipv4:
13.58.86.183
ipv4:
34.209.181.84
ipv4:
35.161.82.137
ipv4:
52.14.70.114
ipv4:
52.15.230.220
ipv4:
52.15.208.139
ipv4:
52.15.62.153
ipv4:
13.58.58.6
ipv4:
54.71.252.65
ipv4:
52.28.49.94
ipv4:
52.29.41.175
ipv4:
52.29.197.69
ipv4:
52.48.124.108
ipv4:
54.240.60.174/31
ipv4:
35.160.0.242
ipv4:
34.213.36.118

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

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:

plesk.epub.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