SPF Check: ooeg.at

Check SPF record for ooeg.at: ⊳Does a valid SPF record exist? ⊳What does it do? ⊳Which IPs are legitimate to send emails?

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.

1. Specify domain name

Your data

Change specifications
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
Lookup for the domain:
ooeg.at
IP address to be checked:
no IP address specified
Loading...
Summary
An SPF record was found for the domain ooeg.at. The syntax check of the SPF record does not show any obvious errors. The SPF record for ooeg.at is valid. In total 26 IP address(es) were authorized by the SPF record to send emails. The SPF record analysis was performed on 25.09.2020 at 09:11:41 clock.

Let us check your SPF record or create a valid entry
Our experts will advise you at a fixed price including risk check for your domain. Avoid the risk of third parties misusing your domain. 30 days free reviews with functional guarantee.

Evaluation for the domain ooeg.at 

Nameserverset:
adns1.utanet.at
dns2.gespag.at
dns1.gespag.at
adns2.utanet.at
Determined SPF record:
Legitimated IP addresses:
SPF-Syntax Check:
Analysis result of the SPF record for the domain: ooeg.at

SPF record available?

We found an SPF record for the domain.

v=spf1

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

smtp.gespag.at

Additionally authorized IPv4 addresses

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

172.25.4.22/32
172.25.4.33/32
172.25.6.25/32
172.25.8.22/32
172.25.10.25/32
193.171.22.46/32
172.25.14.28/31
193.186.45.101/32
193.186.45.196/32
193.186.46.0/24
193.186.47.20/28
193.186.47.22/32
193.186.47.44/32
193.186.47.207/32
193.186.47.208/32
193.186.52.41/32
193.186.52.97/32
193.186.52.98/32
193.186.52.99/32
193.186.52.120/32
193.186.52.151/32
193.186.53.180/32
193.186.60.36/32
193.186.60.164/32
193.186.60.166/32

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.

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

Additional external SPF records

We could not find any other records authorized in SPF-Record

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 )

Unknown mechanisms

No unknown mechanisms were found in the SPF record.

How secure are your domains and where are the dangers lurking?

Domain risks are often underestimated

A current study by BITKOM reports on the alarming increase in cyber attacks on German companies, the ICANN warns of attacks on the global domain name system and the Federal Office for Information Security (BSI) sees significant risk potential in dealing with domain name. Unfortunately, these risks come into play every day, although this damage could have been prevented.

What should companies know and what can they do?

Practical and with many examples, the over 20-page eBook deals with the basics of domain risk management, specifies legal obligations and deals with responsibilities and liability issues. Numerous domain risks (e.g. "Domain Hijacking") are clearly described and the risk assessment and possible consequences are discussed.

Checklist: What about my own domain risks?

The Risk Atlas supports domain managers to get a first impression of their own risk potential in the company. The checklist includes 53 questions on 14 risk areas and enables a quick introduction to the topic.

⮩ Secure white paper "Domain Risk Management" for free

Recently performed SPF lookups

Server IP Address

We have determined the following IP address for the domain:

193.186.49.161

Reverse address

We have determined the following name for the server IP address:

193.186.49.161

© 2012 - 2020 nicmanager.com