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

The SPF record analysis was performed on 02.11.2024 at 01:34:28 clock.

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

Nameserverset:
ns2.lcgindia.com
ns1.lcgindia.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
103.50.160.20 PUBLIC-DOMAIN-REGISTRY blacklist 
152.42.233.210 DIGITALOCEAN-ASN blacklist 
134.209.110.97/32
DIGITALOCEAN-ASN blacklist 
121.240.7.128/28
TATA Communications formerly VSNL is Leading ISP blacklist 
121.240.7.0/25
TATA Communications formerly VSNL is Leading ISP blacklist 
121.240.7.192/30
TATA Communications formerly VSNL is Leading ISP blacklist 
121.240.11.0/26
TATA Communications formerly VSNL is Leading ISP blacklist 
121.240.21.0/25
TATA Communications formerly VSNL is Leading ISP blacklist 
124.7.138.224/27
Sify Limited blacklist 
221.134.197.192/26
Sify Limited blacklist 
121.243.77.64/26
TATA Communications formerly VSNL is Leading ISP blacklist 
216.55.99.144 LEVEL3 blacklist 
216.55.104.161 LEVEL3 blacklist 
216.55.104.162 LEVEL3 blacklist 
216.55.104.163 LEVEL3 blacklist 
115.114.107.112/29
TATA Communications formerly VSNL is Leading ISP blacklist 
115.114.59.138/30
TATA Communications formerly VSNL is Leading ISP blacklist 
115.114.8.144/29
TATA Communications formerly VSNL is Leading ISP blacklist 
115.114.9.60/30
TATA Communications formerly VSNL is Leading ISP blacklist 
115.114.51.192/29
TATA Communications formerly VSNL is Leading ISP blacklist 
115.114.17.18/30
TATA Communications formerly VSNL is Leading ISP blacklist 
219.65.86.0/29
TATA Communications formerly VSNL is Leading ISP blacklist 
59.145.16.128/26
BHARTI Airtel Ltd. blacklist 
14.143.133.32/28
TATA Communications formerly VSNL is Leading ISP blacklist 
121.242.118.128/26
TATA Communications formerly VSNL is Leading ISP 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 
167.89.0.0/17
SENDGRID blacklist 
208.117.48.0/20
SENDGRID blacklist 
50.31.32.0/19
SENDGRID blacklist 
198.37.144.0/20
SENDGRID blacklist 
198.21.0.0/21
SENDGRID blacklist 
192.254.112.0/20
SENDGRID blacklist 
168.245.0.0/17
SENDGRID blacklist 
149.72.0.0/16
AMAZON-AES blacklist 
159.183.0.0/16
SENDGRID blacklist 
223.165.113.0/24
SENDGRID blacklist 
223.165.115.0/24
SENDGRID blacklist 
223.165.118.0/23
SENDGRID blacklist 
223.165.120.0/23
SENDGRID blacklist 
188.166.236.155 DIGITALOCEAN-ASN blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: uniklinger.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

103.50.160.20

Additionally authorized A-records?

In addition to the A-records stored in the DNS, we were able to find further records authorized in the SPF-record

152.42.233.210
188.166.236.155

Additionally authorized IPv4 addresses

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

134.209.110.97/32

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
include:_spfnew.logix.in
v=spf1 ip4:121.240.7.128/28 ip4:121.240.7.0/25 ip4:121.240.7.192/30 ip4:121.240.11.0/26 ip4:121.240.21.0/25 ip4:124.7.138.224/27 ip4:221.134.197.192/26 ip4:121.243.77.64/26 ip4:216.55.99.144 ip4:216.55.104.161 ip4:216.55.104.162 ip4:216.55.104.163 include:_netblock.logix.in ~all
ipv4:
121.240.7.128/28
ipv4:
121.240.7.0/25
ipv4:
121.240.7.192/30
ipv4:
121.240.11.0/26
ipv4:
121.240.21.0/25
ipv4:
124.7.138.224/27
ipv4:
221.134.197.192/26
ipv4:
121.243.77.64/26
ipv4:
216.55.99.144
ipv4:
216.55.104.161
ipv4:
216.55.104.162
ipv4:
216.55.104.163
include:_netblock.logix.in
v=spf1 ip4:115.114.107.112/29 ip4:115.114.59.138/30 ip4:115.114.8.144/29 ip4:115.114.9.60/30 ip4:115.114.51.192/29 ip4:115.114.17.18/30 ip4:219.65.86.0/29 ip4:59.145.16.128/26 ip4:14.143.133.32/28 ip4:121.242.118.128/26 ~all
ipv4:
115.114.107.112/29
ipv4:
115.114.59.138/30
ipv4:
115.114.8.144/29
ipv4:
115.114.9.60/30
ipv4:
115.114.51.192/29
ipv4:
115.114.17.18/30
ipv4:
219.65.86.0/29
ipv4:
59.145.16.128/26
ipv4:
14.143.133.32/28
ipv4:
121.242.118.128/26
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:sendgrid.net
v=spf1 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 include:ab.sendgrid.net ~all
ipv4:
167.89.0.0/17
ipv4:
208.117.48.0/20
ipv4:
50.31.32.0/19
ipv4:
198.37.144.0/20
ipv4:
198.21.0.0/21
ipv4:
192.254.112.0/20
ipv4:
168.245.0.0/17
ipv4:
149.72.0.0/16
ipv4:
159.183.0.0/16
include:ab.sendgrid.net
v=spf1 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ~all
ipv4:
223.165.113.0/24
ipv4:
223.165.115.0/24
ipv4:
223.165.118.0/23
ipv4:
223.165.120.0/23

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

bh-in-37.webhostbox.net

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