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

The SPF record analysis was performed on 29.09.2024 at 03:28:12 clock.

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

Nameserverset:
rodrigo.ns.cloudflare.com
lily.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
52.101.73.26 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.73.4 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.68.3 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.68.15 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
172.67.28.174 - CLOUDFLARENET blacklist 
104.22.70.143 - CLOUDFLARENET blacklist 
104.22.71.143 - CLOUDFLARENET blacklist 
2606:4700:10:0:0:0:6816:468f - CLOUDFLARENET blacklist 
2606:4700:10:0:0:0:6816:478f - CLOUDFLARENET blacklist 
2606:4700:10:0:0:0:ac43:1cae - CLOUDFLARENET 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 
198.245.81.0/24
SALESFORCE blacklist 
136.147.176.0/24
SALESFORCE blacklist 
13.111.0.0/16
SALESFORCE blacklist 
136.147.182.0/24
SALESFORCE blacklist 
136.147.135.0/24
SALESFORCE blacklist 
199.122.123.0/24
SALESFORCE blacklist 
88.211.140.64/26
Vodafone Libertel B.V. blacklist 
82.201.71.103 Vancis IP B.V. blacklist 
212.103.86.20 NTS workspace AG blacklist 
212.17.51.66 Magnet Networks Limited blacklist 
82.201.64.186 Vancis IP B.V. blacklist 
87.116.5.160/28
GlobalConnect A/S blacklist 
31.27.99.145 Vodafone Italia S.p.A. blacklist 
31.27.99.193 Vodafone Italia S.p.A. blacklist 
122.227.167.186/32
Chinanet blacklist 
75.127.227.234 CABLE-NET-1 blacklist 
219.92.247.185 TM TECHNOLOGY SERVICES SDN. BHD. blacklist 
195.53.119.210 Telefonica De Espana S.a.u. blacklist 
195.81.184.64/27
GTT Communications Inc. blacklist 
83.219.88.104 Vancis IP B.V. blacklist 
60.242.143.170 TPG Telecom Limited blacklist 
194.228.218.98 O2 Czech Republic, a.s. blacklist 
202.75.57.189 - blacklist 
217.115.197.67 Vancis IP B.V. blacklist 
31.27.96.193 Vodafone Italia S.p.A. blacklist 
82.192.79.122 LeaseWeb Netherlands B.V. blacklist 
185.36.133.199 Go-Trex Holding BV blacklist 
51.91.254.58 OVH SAS blacklist 
37.187.47.120 OVH SAS blacklist 
121.190.190.99 Korea Telecom blacklist 
61.175.202.238/32
Chinanet blacklist 
51.91.254.58 OVH SAS blacklist 
31.27.99.145 Vodafone Italia S.p.A. blacklist 
31.27.96.193 Vodafone Italia S.p.A. blacklist 
82.201.32.212 Vancis IP B.V. blacklist 
82.201.60.198 Vancis IP B.V. blacklist 
213.209.226.44 Acantho S.p.a blacklist 
213.209.226.37 Acantho S.p.a blacklist 
82.201.66.128/28
Vancis IP B.V. blacklist 
83.219.92.0/25
Vancis IP B.V. blacklist 
82.201.64.228 Vancis IP B.V. blacklist 
213.133.46.8 Vancis IP B.V. blacklist 
81.24.63.0/27
Vancis IP B.V. blacklist 
217.115.197.0/25
Vancis IP B.V. blacklist 
2001:9a0:2010:2:25::/64
Vancis IP B.V. blacklist 
207.211.63.183 NAVISITE-EAST-2 blacklist 
208.116.180.100 GTT Communications Inc. blacklist 
208.116.180.104 GTT Communications Inc. blacklist 
162.218.1.205 SUPRANET-WIS blacklist 
162.218.1.206 SUPRANET-WIS blacklist 
162.218.1.150 SUPRANET-WIS blacklist 
162.218.0.230 SUPRANET-WIS blacklist 
54.240.57.47 AMAZON-02 blacklist 
54.240.57.46 AMAZON-02 blacklist 
68.179.109.125 TRGO blacklist 
40.107.6.49 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
82.193.164.111/32
Telenor Norge AS blacklist 
80.197.60.32/29
TDC Holding A/S blacklist 
154.14.55.140 GTT Communications Inc. blacklist 
69.174.127.2 GTT Communications Inc. blacklist 
14.201.108.59 TPG Telecom Limited blacklist 
123.243.157.179 TPG Telecom Limited blacklist 
123.243.64.43 TPG Telecom Limited blacklist 
27.33.174.170 TPG Telecom Limited blacklist 
60.240.234.251 TPG Telecom Limited blacklist 
14.200.111.59 TPG Telecom Limited blacklist 
192.200.190.165/30
GOOGLE-CLOUD-PLATFORM blacklist 
104.195.80.16/28
- blacklist 
192.200.181.144/28
- blacklist 
174.37.85.64/28
SOFTLAYER blacklist 
75.126.150.248/30
SOFTLAYER blacklist 
63.141.144.128/28
- blacklist 
104.195.127.0/28
GOOGLE-CLOUD-PLATFORM blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: ammega.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

172.67.28.174
104.22.70.143
104.22.71.143
2606:4700:10:0:0:0:6816:468f
2606:4700:10:0:0:0:6816:478f
2606:4700:10:0:0:0:ac43:1cae

Are the registered mail servers allowed to send e-mails?

The mechanism 'mx' was set in the SPF entry. The following hosts are allowed to send

ammega-com.mail.protection.outlook.com
ammega-com.mail.protection.outlook.com
ammega-com.mail.protection.outlook.com
ammega-com.mail.protection.outlook.com

Additionally authorized IPv4 addresses

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

207.211.63.183
208.116.180.100
208.116.180.104
162.218.1.205
162.218.1.206
162.218.1.150
162.218.0.230
54.240.57.47
54.240.57.46
68.179.109.125
40.107.6.49
82.193.164.111/32
80.197.60.32/29
154.14.55.140
69.174.127.2
14.201.108.59
123.243.157.179
123.243.64.43
27.33.174.170
60.240.234.251
14.200.111.59
192.200.190.165/30
104.195.80.16/28
192.200.181.144/28
174.37.85.64/28
75.126.150.248/30
63.141.144.128/28
104.195.127.0/28

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:et._spf.pardot.com
v=spf1 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/16 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.0/24 -all
ipv4:
198.245.81.0/24
ipv4:
136.147.176.0/24
ipv4:
13.111.0.0/16
ipv4:
136.147.182.0/24
ipv4:
136.147.135.0/24
ipv4:
199.122.123.0/24
include:spf1.ammega.info
v=spf1 ip4:88.211.140.64/26 ip4:82.201.71.103 ip4:212.103.86.20 ip4:212.17.51.66 ip4:82.201.64.186 ip4:87.116.5.160/28 ip4:31.27.99.145 ip4:31.27.99.193 ip4:122.227.167.186/32 ip4:75.127.227.234 ip4:219.92.247.185 ip4:195.53.119.210 ip4:195.81.184.64/27 ip4:83.219.88.104 ip4:60.242.143.170 -all
ipv4:
88.211.140.64/26
ipv4:
82.201.71.103
ipv4:
212.103.86.20
ipv4:
212.17.51.66
ipv4:
82.201.64.186
ipv4:
87.116.5.160/28
ipv4:
31.27.99.145
ipv4:
31.27.99.193
ipv4:
122.227.167.186/32
ipv4:
75.127.227.234
ipv4:
219.92.247.185
ipv4:
195.53.119.210
ipv4:
195.81.184.64/27
ipv4:
83.219.88.104
ipv4:
60.242.143.170
include:spf2.ammega.info
v=spf1 ip4:194.228.218.98 ip4:202.75.57.189 ip4:217.115.197.67 ip4:31.27.96.193 ip4:82.192.79.122 ip4:185.36.133.199 ip4:51.91.254.58 ip4:37.187.47.120 ip4:121.190.190.99 ip4:61.175.202.238/32 ip4:51.91.254.58 ip4:31.27.99.145 ip4:31.27.96.193 ip4:82.201.32.212 ip4:82.201.60.198 ip4:213.209.226.44 ip4:213.209.226.37 -all
ipv4:
194.228.218.98
ipv4:
202.75.57.189
ipv4:
217.115.197.67
ipv4:
31.27.96.193
ipv4:
82.192.79.122
ipv4:
185.36.133.199
ipv4:
51.91.254.58
ipv4:
37.187.47.120
ipv4:
121.190.190.99
ipv4:
61.175.202.238/32
ipv4:
51.91.254.58
ipv4:
31.27.99.145
ipv4:
31.27.96.193
ipv4:
82.201.32.212
ipv4:
82.201.60.198
ipv4:
213.209.226.44
ipv4:
213.209.226.37
include:spfinclude.werkonline.nu
v=spf1 ip4:82.201.66.128/28 ip4:83.219.92.0/25 ip4:82.201.64.228 ip4:213.133.46.8 ip4:81.24.63.0/27 ip4:217.115.197.0/25 ip6:2001:9a0:2010:2:25::/64 ?all
ipv4:
82.201.66.128/28
ipv4:
83.219.92.0/25
ipv4:
82.201.64.228
ipv4:
213.133.46.8
ipv4:
81.24.63.0/27
ipv4:
217.115.197.0/25
ipv6:
2001:9a0:2010:2:25::/64
include:_spf.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all

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

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.

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

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