SPF Check:
averis.biz

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 averis.biz.
The SPF record for averis.biz 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 01.11.2024 at 11:38:38 clock.

Lookup for the domain:
averis.biz
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 averis.biz 

Nameserverset:
dns1.cscdns.net
dns2.cscdns.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
34.223.36.122 AMAZON-02 blacklist 
34.223.36.121 AMAZON-02 blacklist 
3.93.93.51 AMAZON-AES blacklist 
34.223.36.123 AMAZON-02 blacklist 
3.93.93.53 AMAZON-AES blacklist 
3.93.93.52 AMAZON-AES blacklist 
3.93.93.52 AMAZON-AES blacklist 
34.223.36.123 AMAZON-02 blacklist 
34.223.36.122 AMAZON-02 blacklist 
34.223.36.121 AMAZON-02 blacklist 
3.93.93.53 AMAZON-AES blacklist 
3.93.93.51 AMAZON-AES blacklist 
3.93.93.52 AMAZON-AES blacklist 
3.93.93.53 AMAZON-AES blacklist 
34.223.36.123 AMAZON-02 blacklist 
34.223.36.121 AMAZON-02 blacklist 
3.93.93.51 AMAZON-AES blacklist 
34.223.36.122 AMAZON-02 blacklist 
3.93.93.51 AMAZON-AES blacklist 
3.93.93.53 AMAZON-AES blacklist 
34.223.36.122 AMAZON-02 blacklist 
34.223.36.123 AMAZON-02 blacklist 
34.223.36.121 AMAZON-02 blacklist 
3.93.93.52 AMAZON-AES blacklist 
210.3.132.46 HGC Global Communications Limited blacklist 
210.3.132.50 HGC Global Communications Limited blacklist 
218.255.107.179 HKBN Enterprise Solutions HK Limited blacklist 
66.96.214.7 MyRepublic Ltd. blacklist 
116.92.233.46 HKBN Enterprise Solutions HK Limited blacklist 
116.92.233.50 HKBN Enterprise Solutions HK Limited blacklist 
124.155.213.38 StarHub Ltd blacklist 
182.23.115.179 PT Aplikanusa Lintasarta blacklist 
175.143.6.74 TM TECHNOLOGY SERVICES SDN. BHD. blacklist 
203.126.166.212 SingNet blacklist 
203.126.166.214 SingNet blacklist 
114.6.224.37 INDOSAT Internet Network Provider blacklist 
218.188.90.231 HGC Global Communications Limited blacklist 
218.188.90.228 HGC Global Communications Limited blacklist 
36.89.59.50 PT Telekomunikasi Indonesia blacklist 
222.124.195.86 PT Telekomunikasi Indonesia blacklist 
222.124.195.85 PT Telekomunikasi Indonesia blacklist 
222.174.154.100 Chinanet blacklist 
221.224.206.153 Chinanet blacklist 
54.255.171.71 AMAZON-02 blacklist 
202.83.193.157 SingTel Hong Kong Limited blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: averis.biz

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

alt2.us.email.fireeyecloud.com
alt2.us.email.fireeyecloud.com
alt2.us.email.fireeyecloud.com
alt2.us.email.fireeyecloud.com
alt2.us.email.fireeyecloud.com
alt2.us.email.fireeyecloud.com
primary.us.email.fireeyecloud.com
primary.us.email.fireeyecloud.com
primary.us.email.fireeyecloud.com
primary.us.email.fireeyecloud.com
primary.us.email.fireeyecloud.com
primary.us.email.fireeyecloud.com
alt1.us.email.fireeyecloud.com
alt1.us.email.fireeyecloud.com
alt1.us.email.fireeyecloud.com
alt1.us.email.fireeyecloud.com
alt1.us.email.fireeyecloud.com
alt1.us.email.fireeyecloud.com
alt3.us.email.fireeyecloud.com
alt3.us.email.fireeyecloud.com
alt3.us.email.fireeyecloud.com
alt3.us.email.fireeyecloud.com
alt3.us.email.fireeyecloud.com
alt3.us.email.fireeyecloud.com

Additional external SPF records

We could find other records authorized in the SPF record

include:spfa.averis.biz
v=spf1 ip4:210.3.132.46 ip4:210.3.132.50 ip4:218.255.107.179 ip4:66.96.214.7 ip4:116.92.233.46 ip4:116.92.233.50 ip4:124.155.213.38 -all
ipv4:
210.3.132.46
ipv4:
210.3.132.50
ipv4:
218.255.107.179
ipv4:
66.96.214.7
ipv4:
116.92.233.46
ipv4:
116.92.233.50
ipv4:
124.155.213.38
include:spfb.averis.biz
v=spf1 ip4:182.23.115.179 ip4:175.143.6.74 ip4:203.126.166.212 ip4:203.126.166.214 ip4:114.6.224.37 ip4:218.188.90.231 ip4:218.188.90.228 ip4:36.89.59.50 ip4:222.124.195.86 ip4:222.124.195.85 -all
ipv4:
182.23.115.179
ipv4:
175.143.6.74
ipv4:
203.126.166.212
ipv4:
203.126.166.214
ipv4:
114.6.224.37
ipv4:
218.188.90.231
ipv4:
218.188.90.228
ipv4:
36.89.59.50
ipv4:
222.124.195.86
ipv4:
222.124.195.85
include:spfc.averis.biz
v=spf1 ip4:222.174.154.100 ip4:221.224.206.153 ip4:54.255.171.71 ip4:202.83.193.157 -all
ipv4:
222.174.154.100
ipv4:
221.224.206.153
ipv4:
54.255.171.71
ipv4:
202.83.193.157

E-Mail handling

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

-all
Fail (non-compliant e-mails are rejected)

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

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:

165.160.15.20

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