Lookup

Sender Policy Framework

Specify domain name

Your data

Change specifications
Enter a domain to be checked for the SPF record
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:
huck.pl
IP address to be checked:
no IP address specified
Loading...

Evaluation for the domain huck.pl 

Determined SPF record:
Nameserverset:
dns.home.pl
dns3.home.pl
dns2.home.pl
Analysis result of the SPF record for the domain: huck.pl

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

212.77.229.237

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

serwer1797802.home.pl

Additionally authorized IPv4 addresses

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

46.242.241.29

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.mediatis.de
v=spf1 ip4:212.77.224.0/19 ip4:62.96.5.0/24 ip4:13.52.45.25 ip4:35.169.217.61 ip4:18.194.228.146 ~all
ipv4:
212.77.224.0/19
ipv4:
62.96.5.0/24
ipv4:
13.52.45.25
ipv4:
35.169.217.61
ipv4:
18.194.228.146

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

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 )

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

Server IP Address

We have determined the following IP address for the domain:

212.77.229.237

Reverse address

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

www.huck.pl

© 2012 - 2020 nicmanager.com