SPF Check:
mirrorservice.org

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

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€

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

The SPF record analysis was performed on 06.05.2024 at 08:55:06 clock.

Lookup for the domain:
mirrorservice.org
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 mirrorservice.org 

Nameserverset:
ns1.bishnet.net
dns0.mirrorservice.org
dns2.mirrorservice.org
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
129.12.21.31 Jisc Services Limited blacklist 
129.12.21.32/29
Jisc Services Limited blacklist 
129.12.21.31 Jisc Services Limited 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/14
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 
130.88.200.144 Jisc Services Limited blacklist 
130.88.200.145 Jisc Services Limited blacklist 
130.88.200.93 Jisc Services Limited blacklist 
130.88.200.94 Jisc Services Limited blacklist 
162.247.216.0/22
QUALTRICS-01 blacklist 
172.23.16.6 - - blacklist 
173.231.138.192/27
SINGLEHOP-LLC blacklist 
173.231.139.0/24
SINGLEHOP-LLC blacklist 
173.231.176.0/21
SINGLEHOP-LLC blacklist 
173.231.184.0/21
SINGLEHOP-LLC blacklist 
176.32.228.1 Host Europe GmbH blacklist 
193.60.48.95 Jisc Services Limited blacklist 
207.46.163.24 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
212.219.56.128/26
Jisc Services Limited blacklist 
213.199.154.143 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
213.199.154.207 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
213.199.154.208 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
213.199.154.209 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
213.206.140.0/22
WPM Software Ltd blacklist 
216.119.209.33 MASTER-7-AS blacklist 
216.119.217.33 MASTER-7-AS blacklist 
216.32.180.184 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
216.32.181.181 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
216.32.181.184 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
46.18.217.114 Virtual1 Limited blacklist 
50.31.59.56 SENDGRID blacklist 
51.141.45.116 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
69.20.10.80/29
RACKSPACE blacklist 
69.20.36.98 RACKSPACE blacklist 
69.20.41.72/27
RACKSPACE blacklist 
69.20.90.0/26
RACKSPACE blacklist 
78.129.142.199 Iomart Cloud Services Limited blacklist 
78.129.199.225 Iomart Cloud Services Limited blacklist 
89.167.234.245 GTT Communications Inc. blacklist 
89.167.234.247 GTT Communications Inc. blacklist 
94.229.173.65/27
Ans Academy Limited blacklist 
95.128.129.3 Fast4networks Ltd blacklist 
212.58.50.240 TalkTalk blacklist 
185.194.168.25 Space Data Centres Ltd blacklist 
82.165.139.9 IONOS SE blacklist 
77.68.81.70 IONOS SE blacklist 
129.12.20.193/28
Jisc Services Limited blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: mirrorservice.org

SPF record available?

We found an SPF record for the domain.

v=spf1

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

mxmas.kent.ac.uk

Additionally authorized MX records

In addition to the MX records stored in the DNS, we were able to find other records authorized in the SPF record

kent.ac.uk

Additionally authorized IPv4 addresses

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

129.12.21.32/29

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/14 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/14
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_whitelist.kent.ac.uk
v=spf1 ip4:130.88.200.144 ip4:130.88.200.145 ip4:130.88.200.93 ip4:130.88.200.94 ip4:162.247.216.0/22 ip4:172.23.16.6 ip4:173.231.138.192/27 ip4:173.231.139.0/24 ip4:173.231.176.0/21 ip4:173.231.184.0/21 ip4:176.32.228.1 ip4:193.60.48.95 ip4:207.46.163.24 ip4:212.219.56.128/26 ip4:213.199.154.143 ip4:213.199.154.207 ip4:213.199.154.208 ip4:213.199.154.209 ip4:213.206.140.0/22 ip4:216.119.209.33 ip4:216.119.217.33 ip4:216.32.180.184 ip4:216.32.181.181 ip4:216.32.181.184 ip4:46.18.217.114 ip4:50.31.59.56 ip4:51.141.45.116 ip4:69.20.10.80/29 ip4:69.20.36.98 ip4:69.20.41.72/27 ip4:69.20.90.0/26 ip4:78.129.142.199 ip4:78.129.199.225 ip4:89.167.234.245 ip4:89.167.234.247 ip4:94.229.173.65/27 ip4:95.128.129.3 ip4:212.58.50.240 ip4:185.194.168.25 ip4:82.165.139.9 ip4:77.68.81.70 ip4:129.12.20.193/28 -all
ipv4:
130.88.200.144
ipv4:
130.88.200.145
ipv4:
130.88.200.93
ipv4:
130.88.200.94
ipv4:
162.247.216.0/22
ipv4:
172.23.16.6
ipv4:
173.231.138.192/27
ipv4:
173.231.139.0/24
ipv4:
173.231.176.0/21
ipv4:
173.231.184.0/21
ipv4:
176.32.228.1
ipv4:
193.60.48.95
ipv4:
207.46.163.24
ipv4:
212.219.56.128/26
ipv4:
213.199.154.143
ipv4:
213.199.154.207
ipv4:
213.199.154.208
ipv4:
213.199.154.209
ipv4:
213.206.140.0/22
ipv4:
216.119.209.33
ipv4:
216.119.217.33
ipv4:
216.32.180.184
ipv4:
216.32.181.181
ipv4:
216.32.181.184
ipv4:
46.18.217.114
ipv4:
50.31.59.56
ipv4:
51.141.45.116
ipv4:
69.20.10.80/29
ipv4:
69.20.36.98
ipv4:
69.20.41.72/27
ipv4:
69.20.90.0/26
ipv4:
78.129.142.199
ipv4:
78.129.199.225
ipv4:
89.167.234.245
ipv4:
89.167.234.247
ipv4:
94.229.173.65/27
ipv4:
95.128.129.3
ipv4:
212.58.50.240
ipv4:
185.194.168.25
ipv4:
82.165.139.9
ipv4:
77.68.81.70
ipv4:
129.12.20.193/28
include:spf-whitelist.kent.ac.uk

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.

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:

www.mirrorservice.org

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