SPF Check:
rcm.ac.uk

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 rcm.ac.uk.
The SPF record for rcm.ac.uk 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, 45 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 23.12.2024 at 02:46:18 clock.

Lookup for the domain:
rcm.ac.uk
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 rcm.ac.uk 

Nameserverset:
ns12.ja.net
ns10.ja.net
ns11.ja.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
54.229.2.165 AMAZON-02 blacklist 
52.30.130.201 AMAZON-02 blacklist 
80.6.91.150 Virgin Media blacklist 
34.198.56.55 AMAZON-AES blacklist 
194.81.216.120 Jisc Services Limited blacklist 
34.110.180.34 GOOGLE-CLOUD-PLATFORM blacklist 
18.245.143.37 AMAZON-02 blacklist 
18.245.143.64 AMAZON-02 blacklist 
18.245.143.90 AMAZON-02 blacklist 
18.245.143.75 AMAZON-02 blacklist 
104.18.37.249 - CLOUDFLARENET blacklist 
172.64.150.7 - CLOUDFLARENET blacklist 
3.8.217.160 AMAZON-02 blacklist 
2606:4700:4400::ac40:9607 - CLOUDFLARENET blacklist 
2606:4700:4400::6812:25f9 - CLOUDFLARENET blacklist 
2a05:d01c:497:732:b5f2:33ae:1c96:6e39 AMAZON-02 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 
85.158.136.0/21
- blacklist 
193.109.254.0/23
- blacklist 
194.106.220.0/23
- blacklist 
195.245.230.0/23
GOOGLE-CLOUD-PLATFORM blacklist 
95.131.104.0/21
- blacklist 
46.226.48.0/21
- blacklist 
216.82.240.0/20
- blacklist 
67.219.240.0/20
AMAZON-AES blacklist 
117.120.16.0/21
AMAZON-02 blacklist 
103.9.96.0/22
GOOGLE-CLOUD-PLATFORM blacklist 
54.206.1.219 AMAZON-02 blacklist 
54.252.191.67 AMAZON-02 blacklist 
52.19.235.69 AMAZON-02 blacklist 
52.19.41.236 AMAZON-02 blacklist 
13.54.130.0 AMAZON-02 blacklist 
3.105.94.134 AMAZON-02 blacklist 
34.252.205.76 AMAZON-02 blacklist 
18.200.192.158 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: rcm.ac.uk

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.229.2.165
52.30.130.201
80.6.91.150
34.198.56.55
194.81.216.120
34.110.180.34
18.245.143.37
18.245.143.64
18.245.143.90
18.245.143.75
104.18.37.249
172.64.150.7
3.8.217.160

Additionally authorized IPv6 addresses

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

2606:4700:4400::ac40:9607
2606:4700:4400::6812:25f9
2a05:d01c:497:732:b5f2:33ae:1c96:6e39

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.messagelabs.com
v=spf1 include:nets1.spf.messagelabs.com include:nets2.spf.messagelabs.com ~all
include:nets1.spf.messagelabs.com
v=spf1 ip4:85.158.136.0/21 ip4:193.109.254.0/23 ip4:194.106.220.0/23 ip4:195.245.230.0/23 ip4:95.131.104.0/21 ip4:46.226.48.0/21
ipv4:
85.158.136.0/21
ipv4:
193.109.254.0/23
ipv4:
194.106.220.0/23
ipv4:
195.245.230.0/23
ipv4:
95.131.104.0/21
ipv4:
46.226.48.0/21
include:nets2.spf.messagelabs.com
v=spf1 ip4:216.82.240.0/20 ip4:67.219.240.0/20 ip4:117.120.16.0/21 ip4:103.9.96.0/22
ipv4:
216.82.240.0/20
ipv4:
67.219.240.0/20
ipv4:
117.120.16.0/21
ipv4:
103.9.96.0/22
include:mailrelay.t1cloud.com
v=spf1 ip4:54.206.1.219 ip4:54.252.191.67 ip4:52.19.235.69 ip4:52.19.41.236 ip4:13.54.130.0 ip4:3.105.94.134 ip4:34.252.205.76 ip4:18.200.192.158 ~all
ipv4:
54.206.1.219
ipv4:
54.252.191.67
ipv4:
52.19.235.69
ipv4:
52.19.41.236
ipv4:
13.54.130.0
ipv4:
3.105.94.134
ipv4:
34.252.205.76
ipv4:
18.200.192.158

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

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:

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