SPF Check:
mdpweb.net

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 failed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 1 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain mdpweb.net.
The SPF record for mdpweb.net is not valid.
The syntax check resulted in a total of 1 errors.
of the email -Spoofing protection for this domain is not or not sufficiently provided.

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

The SPF record analysis was performed on 19.04.2024 at 22:41:35 clock.

Lookup for the domain:
mdpweb.net
IP address to be checked:
no IP address specified

Have secure SPF record created by expert
from 749€

Order SPF record
  • 1. You send an email to our analysis system
  • 2. We will send you the finished SPF record
  • 3. You implement the SPF record
  • 4. We check the setup final
Have secure SPF record created by expert
from 749€

Evaluation for the domain mdpweb.net 

Nameserverset:
ns3.worldnic.com
ns4.worldnic.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
35.190.247.0/24
GOOGLE-CLOUD-PLATFORM blacklist 
64.233.160.0/19
GOOGLE blacklist 
66.102.0.0/20
GOOGLE blacklist 
66.249.80.0/20
GOOGLE blacklist 
72.14.192.0/18
GOOGLE blacklist 
74.125.0.0/16
GOOGLE blacklist 
108.177.8.0/21
GOOGLE blacklist 
173.194.0.0/16
GOOGLE blacklist 
209.85.128.0/17
GOOGLE blacklist 
216.58.192.0/19
GOOGLE blacklist 
216.239.32.0/19
GOOGLE blacklist 
2001:4860:4000::/36
GOOGLE blacklist 
2404:6800:4000::/36
GOOGLE blacklist 
2607:f8b0:4000::/36
GOOGLE blacklist 
2800:3f0:4000::/36
GOOGLE blacklist 
2a00:1450:4000::/36
GOOGLE blacklist 
2c0f:fb50:4000::/36
GOOGLE blacklist 
172.217.0.0/19
GOOGLE blacklist 
172.217.32.0/20
GOOGLE blacklist 
172.217.128.0/19
GOOGLE blacklist 
172.217.160.0/20
GOOGLE blacklist 
172.217.192.0/19
GOOGLE blacklist 
172.253.56.0/21
GOOGLE blacklist 
172.253.112.0/20
GOOGLE blacklist 
108.177.96.0/19
GOOGLE blacklist 
35.191.0.0/16
GOOGLE blacklist 
130.211.0.0/22
GOOGLE-CLOUD-PLATFORM blacklist 
75.126.84.128/26
SOFTLAYER blacklist 
67.228.8.0/25
SOFTLAYER blacklist 
67.227.149.19 LIQUIDWEB blacklist 
64.56.208.32/27
GREENVIEWDATA blacklist 
67.228.91.90 SOFTLAYER blacklist 
67.228.158.174 SOFTLAYER blacklist 
174.36.44.116/30
SOFTLAYER blacklist 
50.201.66.168 GREENVIEWDATA blacklist 
63.71.8.0/21
ASN-CUST blacklist 
199.30.232.0/21
ASN-CUST blacklist 
74.203.184.0/23
AS-APPRIVER blacklist 
207.195.176.0/20
ASN-CUST blacklist 
54.240.58.238 AMAZON-02 blacklist 
54.240.58.239 AMAZON-02 blacklist 
52.88.164.35 AMAZON-02 blacklist 
52.36.203.184 AMAZON-02 blacklist 
54.213.23.204 AMAZON-02 blacklist 
54.68.232.11 AMAZON-02 blacklist 
35.155.248.228 AMAZON-02 blacklist 
54.71.22.210 AMAZON-02 blacklist 
54.187.161.249 AMAZON-02 blacklist 
18.189.38.231 AMAZON-02 blacklist 
3.128.109.31 AMAZON-02 blacklist 
18.197.93.178 AMAZON-02 blacklist 
199.255.192.0/22
AMAZON-02 blacklist 
199.127.232.0/22
AMAZON-02 blacklist 
54.240.0.0/18
AMAZON-02 blacklist 
69.169.224.0/20
AMAZON-02 blacklist 
23.249.208.0/20
AMAZON-02 blacklist 
23.251.224.0/19
AMAZON-02 blacklist 
76.223.176.0/20
AMAZON-02 blacklist 
52.82.172.0/22
Ningxia West Cloud Data Technology Co.Ltd. blacklist 
54.240.64.0/19
AMAZON-AES blacklist 
54.240.96.0/19
AMAZON-02 blacklist 
76.223.128.0/19
AMAZON-02 blacklist 
216.221.160.0/19
AMAZON-02 blacklist 
199.255.192.0/22
AMAZON-02 blacklist 
199.127.232.0/22
AMAZON-02 blacklist 
54.240.0.0/18
AMAZON-02 blacklist 
69.169.224.0/20
AMAZON-02 blacklist 
23.249.208.0/20
AMAZON-02 blacklist 
23.251.224.0/19
AMAZON-02 blacklist 
76.223.176.0/20
AMAZON-02 blacklist 
52.82.172.0/22
Ningxia West Cloud Data Technology Co.Ltd. blacklist 
54.240.64.0/19
AMAZON-AES blacklist 
54.240.96.0/19
AMAZON-02 blacklist 
76.223.128.0/19
AMAZON-02 blacklist 
216.221.160.0/19
AMAZON-02 blacklist 
208.86.168.7 ULTISOFTASN blacklist 
135.84.68.123 USG-PROD-WEST01 blacklist 
206.152.14.54 USG-TOR-AS blacklist 
135.84.79.54 USG-TOR-AS blacklist 
54.240.30.118 AMAZON-AES blacklist 
54.240.30.125 AMAZON-AES blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: mdpweb.net

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

54.240.30.118
54.240.30.125

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.google.com
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all
include:_netblocks.google.com
v=spf1 ip4:35.190.247.0/24 ip4:64.233.160.0/19 ip4:66.102.0.0/20 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:74.125.0.0/16 ip4:108.177.8.0/21 ip4:173.194.0.0/16 ip4:209.85.128.0/17 ip4:216.58.192.0/19 ip4:216.239.32.0/19 ~all
ipv4:
35.190.247.0/24
ipv4:
64.233.160.0/19
ipv4:
66.102.0.0/20
ipv4:
66.249.80.0/20
ipv4:
72.14.192.0/18
ipv4:
74.125.0.0/16
ipv4:
108.177.8.0/21
ipv4:
173.194.0.0/16
ipv4:
209.85.128.0/17
ipv4:
216.58.192.0/19
ipv4:
216.239.32.0/19
include:_netblocks2.google.com
v=spf1 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ~all
ipv6:
2001:4860:4000::/36
ipv6:
2404:6800:4000::/36
ipv6:
2607:f8b0:4000::/36
ipv6:
2800:3f0:4000::/36
ipv6:
2a00:1450:4000::/36
ipv6:
2c0f:fb50:4000::/36
include:_netblocks3.google.com
v=spf1 ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.253.56.0/21 ip4:172.253.112.0/20 ip4:108.177.96.0/19 ip4:35.191.0.0/16 ip4:130.211.0.0/22 ~all
ipv4:
172.217.0.0/19
ipv4:
172.217.32.0/20
ipv4:
172.217.128.0/19
ipv4:
172.217.160.0/20
ipv4:
172.217.192.0/19
ipv4:
172.253.56.0/21
ipv4:
172.253.112.0/20
ipv4:
108.177.96.0/19
ipv4:
35.191.0.0/16
ipv4:
130.211.0.0/22
include:mdpweb-net.spf.smtp25.com
v=spf1 ip4:75.126.84.128/26 ip4:67.228.8.0/25 ip4:67.227.149.19 ip4:64.56.208.32/27 ip4:67.228.91.90 ip4:67.228.158.174 ip4:174.36.44.116/30 ip4:50.201.66.168 ip4:63.71.8.0/21 ip4:199.30.232.0/21 ip4:74.203.184.0/23 ip4:207.195.176.0/20 ~all
ipv4:
75.126.84.128/26
ipv4:
67.228.8.0/25
ipv4:
67.227.149.19
ipv4:
64.56.208.32/27
ipv4:
67.228.91.90
ipv4:
67.228.158.174
ipv4:
174.36.44.116/30
ipv4:
50.201.66.168
ipv4:
63.71.8.0/21
ipv4:
199.30.232.0/21
ipv4:
74.203.184.0/23
ipv4:
207.195.176.0/20
include:_spf.brainier.com
v=spf1 ip4:54.240.58.238 ip4:54.240.58.239 ip4:52.88.164.35 ip4:52.36.203.184 ip4:54.213.23.204 ip4:54.68.232.11 ip4:35.155.248.228 ip4:54.71.22.210 ip4:54.187.161.249 ip4:18.189.38.231 ip4:3.128.109.31 ip4:18.197.93.178 include:amazonses.com ~all
ipv4:
54.240.58.238
ipv4:
54.240.58.239
ipv4:
52.88.164.35
ipv4:
52.36.203.184
ipv4:
54.213.23.204
ipv4:
54.68.232.11
ipv4:
35.155.248.228
ipv4:
54.71.22.210
ipv4:
54.187.161.249
ipv4:
18.189.38.231
ipv4:
3.128.109.31
ipv4:
18.197.93.178
include:amazonses.com
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:52.82.172.0/22 ip4:54.240.64.0/19 ip4:54.240.96.0/19 ip4:76.223.128.0/19 ip4:216.221.160.0/19 -all
ipv4:
199.255.192.0/22
ipv4:
199.127.232.0/22
ipv4:
54.240.0.0/18
ipv4:
69.169.224.0/20
ipv4:
23.249.208.0/20
ipv4:
23.251.224.0/19
ipv4:
76.223.176.0/20
ipv4:
52.82.172.0/22
ipv4:
54.240.64.0/19
ipv4:
54.240.96.0/19
ipv4:
76.223.128.0/19
ipv4:
216.221.160.0/19
include:amazonses.com (Domain has already been resolved once)
include:_spf.ultipro.com
v=spf1 ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 ip4:135.84.79.54 -all
ipv4:
208.86.168.7
ipv4:
135.84.68.123
ipv4:
206.152.14.54
ipv4:
135.84.79.54

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:

103.95.212.35.bc.googleusercontent.com

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   Connected by Team Internet