SPF Check:
mailgun.co

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

The SPF record analysis was performed on 05.05.2024 at 05:24:11 clock.

Lookup for the domain:
mailgun.co
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 mailgun.co 

Nameserverset:
ns-2042.awsdns-63.co.uk
ns-1011.awsdns-62.net
ns-162.awsdns-20.com
ns-1454.awsdns-53.org
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
18.213.45.180 AMAZON-AES blacklist 
54.147.205.197 AMAZON-AES blacklist 
18.213.159.127 AMAZON-AES blacklist 
52.6.20.110 AMAZON-AES blacklist 
3.222.100.56 AMAZON-AES blacklist 
52.202.203.170 AMAZON-AES blacklist 
54.211.70.132 AMAZON-AES blacklist 
3.234.26.169 AMAZON-AES blacklist 
54.197.154.120 AMAZON-AES blacklist 
72.44.52.71 AMAZON-AES blacklist 
52.55.231.237 AMAZON-AES blacklist 
18.211.55.180 AMAZON-AES blacklist 
100.21.173.16 AMAZON-02 blacklist 
54.213.107.195 AMAZON-02 blacklist 
44.237.58.28 AMAZON-02 blacklist 
54.68.41.21 AMAZON-02 blacklist 
34.216.64.35 AMAZON-02 blacklist 
54.190.215.52 AMAZON-02 blacklist 
34.212.200.183 AMAZON-02 blacklist 
52.32.161.140 AMAZON-02 blacklist 
44.237.110.235 AMAZON-02 blacklist 
54.149.75.234 AMAZON-02 blacklist 
35.162.217.150 AMAZON-02 blacklist 
35.163.207.191 AMAZON-02 blacklist 
18.157.75.126 AMAZON-02 blacklist 
18.158.176.19 AMAZON-02 blacklist 
3.74.55.73 AMAZON-02 blacklist 
3.65.122.213 AMAZON-02 blacklist 
18.197.223.145 AMAZON-02 blacklist 
3.76.161.72 AMAZON-02 blacklist 
18.157.58.83 AMAZON-02 blacklist 
18.156.43.163 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: mailgun.co

SPF record available?

We found an SPF record for the domain.

v=spf1

Will be forwarded to another SPF record?

There is an SPF record that refers to another SPF record Additional entries in this record are therefore ignored.

redirect:_spf.mailgun.co
v=spf1 include:_use1.mailgun.co include:_usw2.mailgun.co include:_euc1.mailgun.co ~all
include:_use1.mailgun.co
v=spf1 ip4:18.213.45.180 ip4:54.147.205.197 ip4:18.213.159.127 ip4:52.6.20.110 ip4:3.222.100.56 ip4:52.202.203.170 ip4:54.211.70.132 ip4:3.234.26.169 ip4:54.197.154.120 ip4:72.44.52.71 ip4:52.55.231.237 ip4:18.211.55.180 ~all
ipv4:
18.213.45.180
ipv4:
54.147.205.197
ipv4:
18.213.159.127
ipv4:
52.6.20.110
ipv4:
3.222.100.56
ipv4:
52.202.203.170
ipv4:
54.211.70.132
ipv4:
3.234.26.169
ipv4:
54.197.154.120
ipv4:
72.44.52.71
ipv4:
52.55.231.237
ipv4:
18.211.55.180
include:_usw2.mailgun.co
v=spf1 ip4:100.21.173.16 ip4:54.213.107.195 ip4:44.237.58.28 ip4:54.68.41.21 ip4:34.216.64.35 ip4:54.190.215.52 ip4:34.212.200.183 ip4:52.32.161.140 ip4:44.237.110.235 ip4:54.149.75.234 ip4:35.162.217.150 ip4:35.163.207.191 ~all
ipv4:
100.21.173.16
ipv4:
54.213.107.195
ipv4:
44.237.58.28
ipv4:
54.68.41.21
ipv4:
34.216.64.35
ipv4:
54.190.215.52
ipv4:
34.212.200.183
ipv4:
52.32.161.140
ipv4:
44.237.110.235
ipv4:
54.149.75.234
ipv4:
35.162.217.150
ipv4:
35.163.207.191
include:_euc1.mailgun.co
v=spf1 ip4:18.157.75.126 ip4:18.158.176.19 ip4:3.74.55.73 ip4:3.65.122.213 ip4:18.197.223.145 ip4:3.76.161.72 ip4:18.157.58.83 ip4:18.156.43.163 ~all
ipv4:
18.157.75.126
ipv4:
18.158.176.19
ipv4:
3.74.55.73
ipv4:
3.65.122.213
ipv4:
18.197.223.145
ipv4:
3.76.161.72
ipv4:
18.157.58.83
ipv4:
18.156.43.163

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

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 )

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

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:

50.56.21.177

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