SPF Check:
ijm.aero

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
Warning: Compliance breach for email deliverability & security

The domain ijm.aero does not fulfil the requirements for optimal deliverability to Google, Yahoo and other email service providers.

Mandatory IT baseline protection measures for email security are not fulfilled. There are risks of email misuse.

Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain ijm.aero.
The SPF record for ijm.aero 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, 31 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 30.11.2024 at 17:34:56 clock.

Lookup for the domain:
ijm.aero
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 ijm.aero 

Nameserverset:
ns2a.dodns.net
ns1a.dodns.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
88.116.228.152/29
Telekom Austria blacklist 
80.122.97.72/29
Telekom Austria blacklist 
37.186.17.120/29
oja.at GmbH blacklist 
5.183.173.128/28
Nessus GmbH blacklist 
77.244.254.128/27
Nessus GmbH blacklist 
212.232.29.192/28
Nessus GmbH blacklist 
77.244.241.64/26
Nessus GmbH blacklist 
77.244.254.80/29
Nessus GmbH blacklist 
217.74.10.0/28
Nessus GmbH blacklist 
217.74.10.144/28
Nessus GmbH blacklist 
92.42.140.240/29
Nessus GmbH blacklist 
84.242.13.0/27
Nessus GmbH blacklist 
5.183.173.144/28
Nessus GmbH blacklist 
13.74.137.176 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.138.216.130 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.114.221.220 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.113.3.253 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.100.56.64 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
137.116.240.241 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.74.144.83 MICROSOFT-CORP-MSN-AS-BLOCK 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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: ijm.aero

SPF record available?

We found an SPF record for the domain.

v=spf1

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.protection.ijm.at
v=spf1 ip4:88.116.228.152/29 ip4:80.122.97.72/29 ip4:37.186.17.120/29 ip4:5.183.173.128/28 -all
ipv4:
88.116.228.152/29
ipv4:
80.122.97.72/29
ipv4:
37.186.17.120/29
ipv4:
5.183.173.128/28
include:spf.protection.laufwerk.it
v=spf1 ip4:77.244.254.128/27 ip4:212.232.29.192/28 ip4:77.244.241.64/26 ip4:77.244.254.80/29 ip4:217.74.10.0/28 ip4:217.74.10.144/28 ip4:92.42.140.240/29 ip4:84.242.13.0/27 ip4:5.183.173.144/28 -all
ipv4:
77.244.254.128/27
ipv4:
212.232.29.192/28
ipv4:
77.244.241.64/26
ipv4:
77.244.254.80/29
ipv4:
217.74.10.0/28
ipv4:
217.74.10.144/28
ipv4:
92.42.140.240/29
ipv4:
84.242.13.0/27
ipv4:
5.183.173.144/28
include:spf-eu.emailsignatures365.com
v=spf1 ip4:13.74.137.176 ip4:52.138.216.130 ip4:40.114.221.220 ip4:40.113.3.253 ip4:23.100.56.64 ip4:137.116.240.241 ip4:13.74.144.83 -all
ipv4:
13.74.137.176
ipv4:
52.138.216.130
ipv4:
40.114.221.220
ipv4:
40.113.3.253
ipv4:
23.100.56.64
ipv4:
137.116.240.241
ipv4:
13.74.144.83
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

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 IPv4 addresses

No explicit IPv4 addresses in the SPF record have been authorised to send

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:

ip077244254093.rev.nessus.at

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