SPF Check:
re2.energy

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 re2.energy.
The SPF record for re2.energy 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, 41 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 05.11.2024 at 13:44:05 clock.

Lookup for the domain:
re2.energy
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 re2.energy 

Nameserverset:
ns1.hosting.de
ns2.hosting.de
ns3.hosting.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
134.0.28.8 Hosting.de GmbH blacklist 
134.0.28.9 Hosting.de GmbH blacklist 
134.0.28.11 Hosting.de GmbH blacklist 
134.0.28.12 Hosting.de GmbH blacklist 
95.129.51.164 Hosting.de GmbH blacklist 
95.129.51.170 Hosting.de GmbH blacklist 
95.129.51.220 Hosting.de GmbH blacklist 
213.160.72.82 Hosting.de GmbH blacklist 
185.11.139.55 Hosting.de GmbH blacklist 
95.129.51.8 Hosting.de GmbH blacklist 
2a03:2900:1:a::8 Hosting.de GmbH blacklist 
2a03:2900:1:a::9 Hosting.de GmbH blacklist 
2a03:2900:1:a::a Hosting.de GmbH blacklist 
2a03:2900:1:a::b Hosting.de GmbH blacklist 
2a03:2900:1:1::6 Hosting.de GmbH blacklist 
2a03:2900:1:1::a Hosting.de GmbH blacklist 
2a03:2900:1:1::b Hosting.de GmbH blacklist 
2a00:17d8:100::261 Hosting.de GmbH blacklist 
2a03:2900:200::101 Hosting.de GmbH blacklist 
2a03:2900:200::1c1 Hosting.de GmbH blacklist 
83.246.65.0/24
kyberio GmbH blacklist 
185.140.204.0/22
HKN GmbH blacklist 
94.100.128.0/20
MK Netzdienste GmbH blacklist 
81.20.94.0/24
QualityHosting AG blacklist 
173.45.18.0/24
AMC blacklist 
52.62.123.207/32
AMAZON-02 blacklist 
52.62.108.212/32
AMAZON-02 blacklist 
129.232.203.80/28
xneelo blacklist 
209.172.38.64/27
IWEB-AS blacklist 
108.163.133.224/27
IWEB-AS blacklist 
193.135.100.0/27
Bluewin blacklist 
199.27.221.76 EPIC-IS blacklist 
216.46.11.238 OPENFACE blacklist 
216.46.11.244 OPENFACE blacklist 
199.27.221.81 EPIC-IS blacklist 
199.27.221.82 EPIC-IS blacklist 
52.62.114.130 AMAZON-02 blacklist 
52.62.125.178 AMAZON-02 blacklist 
92.54.27.0/24
Claranet Limited blacklist 
174.142.136.160/27
IWEB-AS blacklist 
213.160.72.78 Hosting.de GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: re2.energy

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

213.160.72.78

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.hosting.de
v=spf1 ip4:134.0.28.8 ip4:134.0.28.9 ip4:134.0.28.11 ip4:134.0.28.12 ip4:95.129.51.164 ip4:95.129.51.170 ip4:95.129.51.220 ip4:213.160.72.82 ip4:185.11.139.55 ip4:95.129.51.8 ip6:2a03:2900:1:a::8 ip6:2a03:2900:1:a::9 ip6:2a03:2900:1:a::a ip6:2a03:2900:1:a::b ip6:2a03:2900:1:1::6 ip6:2a03:2900:1:1::a ip6:2a03:2900:1:1::b ip6:2a00:17d8:100::261 ip6:2a03:2900:200::101 ip6:2a03:2900:200::1c1 ~all
ipv4:
134.0.28.8
ipv4:
134.0.28.9
ipv4:
134.0.28.11
ipv4:
134.0.28.12
ipv4:
95.129.51.164
ipv4:
95.129.51.170
ipv4:
95.129.51.220
ipv4:
213.160.72.82
ipv4:
185.11.139.55
ipv4:
95.129.51.8
ipv6:
2a03:2900:1:a::8
ipv6:
2a03:2900:1:a::9
ipv6:
2a03:2900:1:a::a
ipv6:
2a03:2900:1:a::b
ipv6:
2a03:2900:1:1::6
ipv6:
2a03:2900:1:1::a
ipv6:
2a03:2900:1:1::b
ipv6:
2a00:17d8:100::261
ipv6:
2a03:2900:200::101
ipv6:
2a03:2900:200::1c1
include:spf.hornetsecurity.com
v=spf1 ip4:83.246.65.0/24 ip4:185.140.204.0/22 ip4:94.100.128.0/20 ip4:81.20.94.0/24 ip4:173.45.18.0/24 ip4:52.62.123.207/32 ip4:52.62.108.212/32 ip4:129.232.203.80/28 ip4:209.172.38.64/27 ip4:108.163.133.224/27 ip4:193.135.100.0/27 ip4:199.27.221.76 ip4:216.46.11.238 ip4:216.46.11.244 ip4:199.27.221.81 ip4:199.27.221.82 ip4:52.62.114.130 ip4:52.62.125.178 ip4:92.54.27.0/24 ip4:174.142.136.160/27 ~all
ipv4:
83.246.65.0/24
ipv4:
185.140.204.0/22
ipv4:
94.100.128.0/20
ipv4:
81.20.94.0/24
ipv4:
173.45.18.0/24
ipv4:
52.62.123.207/32
ipv4:
52.62.108.212/32
ipv4:
129.232.203.80/28
ipv4:
209.172.38.64/27
ipv4:
108.163.133.224/27
ipv4:
193.135.100.0/27
ipv4:
199.27.221.76
ipv4:
216.46.11.238
ipv4:
216.46.11.244
ipv4:
199.27.221.81
ipv4:
199.27.221.82
ipv4:
52.62.114.130
ipv4:
52.62.125.178
ipv4:
92.54.27.0/24
ipv4:
174.142.136.160/27

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

~all
SoftFail (non-compliant e-mails are accepted but marked)

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:

213.160.73.122

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