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

The SPF record analysis was performed on 24.12.2024 at 18:40:58 clock.

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

Nameserverset:
ns2.partner-in.asia
ns1.teldoserver.de
ns2.teldoserver.de
ns3.teldoserver.de
ns1.partner-in.asia
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
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 
80.146.169.1/24
Deutsche Telekom AG blacklist 
62.153.97.85/27
Deutsche Telekom AG blacklist 
217.243.194.1/23
Deutsche Telekom AG blacklist 
87.106.29.124 IONOS SE blacklist 
217.160.165.106 IONOS SE blacklist 
212.211.225.13 q.beyond AG blacklist 
212.211.215.2 q.beyond AG blacklist 
212.211.215.7 q.beyond AG blacklist 
212.211.215.8 q.beyond AG blacklist 
40.113.77.108 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
178.77.121.128/26
PlusServer GmbH blacklist 
158.69.163.48/29
OVH SAS blacklist 
46.4.238.128/29
Hetzner Online GmbH blacklist 
194.42.96.0/23
AMAZON-02 blacklist 
2607:5300:203:fe1::/112
OVH SAS blacklist 
3.122.237.59 AMAZON-02 blacklist 
18.185.29.249 AMAZON-02 blacklist 
3.67.11.109 AMAZON-02 blacklist 
162.55.98.188 Hetzner Online GmbH blacklist 
168.119.122.188 Hetzner Online GmbH blacklist 
94.130.123.88 Hetzner Online GmbH blacklist 
18.197.106.48 AMAZON-02 blacklist 
18.192.61.128 AMAZON-02 blacklist 
168.119.79.18 Hetzner Online GmbH blacklist 
3.127.57.57 AMAZON-02 blacklist 
18.184.74.27 AMAZON-02 blacklist 
18.156.77.186 AMAZON-02 blacklist 
159.69.198.176 Hetzner Online GmbH blacklist 
18.185.56.236 AMAZON-02 blacklist 
52.59.223.36 AMAZON-02 blacklist 
178.203.163.95 Vodafone GmbH blacklist 
52.59.240.85 AMAZON-02 blacklist 
3.125.9.245 AMAZON-02 blacklist 
157.90.110.35 Hetzner Online GmbH blacklist 
3.70.111.115 AMAZON-02 blacklist 
116.202.187.74 Hetzner Online GmbH blacklist 
3.120.134.164 AMAZON-02 blacklist 
18.195.244.214 AMAZON-02 blacklist 
3.66.167.114 AMAZON-02 blacklist 
52.28.240.114 AMAZON-02 blacklist 
88.99.120.4 Hetzner Online GmbH blacklist 
159.69.198.153 Hetzner Online GmbH blacklist 
18.185.177.92 AMAZON-02 blacklist 
3.70.204.162 AMAZON-02 blacklist 
18.156.76.52 AMAZON-02 blacklist 
3.122.206.42 AMAZON-02 blacklist 
3.67.91.22 AMAZON-02 blacklist 
116.202.7.112 Hetzner Online GmbH blacklist 
5.9.58.61 Hetzner Online GmbH blacklist 
52.28.32.151 AMAZON-02 blacklist 
18.195.216.51 AMAZON-02 blacklist 
18.185.13.51 AMAZON-02 blacklist 
3.68.197.230 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: paeffgen.com

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

80.146.169.1/24
62.153.97.85/27
217.243.194.1/23
87.106.29.124
217.160.165.106
212.211.225.13
212.211.215.2
212.211.215.7
212.211.215.8
40.113.77.108

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:spf.crsend.com
v=spf1 ip4:178.77.121.128/26 ip4:158.69.163.48/29 ip4:46.4.238.128/29 ip4:194.42.96.0/23 ip6:2607:5300:203:fe1::/112 ~all
ipv4:
178.77.121.128/26
ipv4:
158.69.163.48/29
ipv4:
46.4.238.128/29
ipv4:
194.42.96.0/23
ipv6:
2607:5300:203:fe1::/112
include:spf1.mailserveradmin.de
v=spf1 ip4:3.122.237.59 ip4:18.185.29.249 ip4:3.67.11.109 ip4:162.55.98.188 ip4:168.119.122.188 ip4:94.130.123.88 ip4:18.197.106.48 ip4:18.192.61.128 ip4:168.119.79.18 ip4:3.127.57.57 ip4:18.184.74.27 ip4:18.156.77.186 ip4:159.69.198.176 ip4:18.185.56.236 ip4:52.59.223.36 ip4:178.203.163.95 ip4:52.59.240.85 ip4:3.125.9.245 ip4:157.90.110.35 ip4:3.70.111.115 ip4:116.202.187.74 ip4:3.120.134.164 ip4:18.195.244.214 ip4:3.66.167.114 ip4:52.28.240.114 ip4:88.99.120.4 ip4:159.69.198.153 ip4:18.185.177.92 ip4:3.70.204.162 ip4:18.156.76.52 ip4:3.122.206.42 ip4:3.67.91.22 ip4:116.202.7.112 ip4:5.9.58.61 ip4:52.28.32.151 ip4:18.195.216.51 ip4:18.185.13.51 ip4:3.68.197.230 ~all
ipv4:
3.122.237.59
ipv4:
18.185.29.249
ipv4:
3.67.11.109
ipv4:
162.55.98.188
ipv4:
168.119.122.188
ipv4:
94.130.123.88
ipv4:
18.197.106.48
ipv4:
18.192.61.128
ipv4:
168.119.79.18
ipv4:
3.127.57.57
ipv4:
18.184.74.27
ipv4:
18.156.77.186
ipv4:
159.69.198.176
ipv4:
18.185.56.236
ipv4:
52.59.223.36
ipv4:
178.203.163.95
ipv4:
52.59.240.85
ipv4:
3.125.9.245
ipv4:
157.90.110.35
ipv4:
3.70.111.115
ipv4:
116.202.187.74
ipv4:
3.120.134.164
ipv4:
18.195.244.214
ipv4:
3.66.167.114
ipv4:
52.28.240.114
ipv4:
88.99.120.4
ipv4:
159.69.198.153
ipv4:
18.185.177.92
ipv4:
3.70.204.162
ipv4:
18.156.76.52
ipv4:
3.122.206.42
ipv4:
3.67.91.22
ipv4:
116.202.7.112
ipv4:
5.9.58.61
ipv4:
52.28.32.151
ipv4:
18.195.216.51
ipv4:
18.185.13.51
ipv4:
3.68.197.230

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 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:

static.42.2.203.116.clients.your-server.de

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