SPF Check: fvhh.net

Check SPF record for fvhh.net: ⊳Does a valid SPF record exist? ⊳What does it do? ⊳Which IPs are legitimate to send emails?

1. Specify domain name

Your data

Change specifications
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
Lookup for the domain:
fvhh.net
IP address to be checked:
no IP address specified
Loading...
Summary
An SPF record was found for the domain fvhh.net. The syntax check of the SPF record does not show any obvious errors. The SPF record for fvhh.net is valid. 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 externally used "includes" can be found in the analysis result. In total 71 IP address(es) were authorized by the SPF record to send emails. The SPF record analysis was performed on 02.12.2021 at 14:29:48 clock.

Let us check your SPF record or create a valid entry
Our experts will advise you at a fixed price including risk check for your domain. Avoid the risk of third parties misusing your domain. 30 days free reviews with functional guarantee.

Evaluation for the domain fvhh.net 

Nameserverset:
ns74.domaincontrol.com
ns73.domaincontrol.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
207.211.31.0/25
NAVISITE-EAST-2 blacklist 
205.139.110.0/24
MIMECAST blacklist 
216.205.24.0/24
MIMECAST blacklist 
170.10.151.0/24
MIMECAST blacklist 
170.10.153.0/24
MIMECAST blacklist 
170.10.129.0/24
MIMECAST blacklist 
63.128.21.0/24
MIMECAST blacklist 
170.10.133.0/24
MIMECAST blacklist 
185.58.84.93/32
Mimecast Services Limited blacklist 
207.211.41.113/32
NAVISITE-EAST-2 blacklist 
207.211.30.64/26
MIMECAST blacklist 
207.211.30.128/25
MIMECAST blacklist 
176.31.7.0/25
OVH SAS blacklist 
178.33.84.64/27
OVH SAS blacklist 
51.178.153.0/24
OVH SAS blacklist 
174.142.128.32/27
IWEB-AS blacklist 
5.135.241.64/26
OVH SAS blacklist 
5.135.31.128/27
OVH SAS blacklist 
188.165.95.224/27
OVH SAS blacklist 
176.31.140.80/28
OVH SAS blacklist 
176.31.69.160/28
OVH SAS blacklist 
176.31.145.240/28
OVH SAS blacklist 
188.165.144.128/28
OVH SAS blacklist 
37.59.169.64/28
OVH SAS blacklist 
37.59.131.32/28
OVH SAS blacklist 
198.50.170.32/28
OVH SAS blacklist 
178.33.9.160/28
OVH SAS blacklist 
51.222.89.0/24
OVH SAS blacklist 
96.45.68.0/24
EZZI-101-BGP blacklist 
162.254.227.0/24
EZZI-101-BGP blacklist 
46.105.146.0/25
OVH SAS blacklist 
5.196.146.128/25
OVH SAS blacklist 
192.99.26.0/25
OVH SAS blacklist 
104.243.65.0/25
EZZI-101-BGP blacklist 
51.254.70.0/26
OVH SAS blacklist 
67.227.85.0/24
AS-COLOAM blacklist 
67.227.87.0/24
AS-COLOAM blacklist 
178.33.242.0/24
OVH SAS blacklist 
216.169.98.0/23
EZZI-101-BGP blacklist 
217.182.181.0/24
OVH SAS blacklist 
54.36.22.0/24
OVH SAS blacklist 
51.38.210.0/24
OVH SAS blacklist 
142.44.153.0/24
OVH SAS blacklist 
104.154.162.117 GOOGLE blacklist 
104.197.223.236 GOOGLE blacklist 
34.66.115.54 GOOGLE-CLOUD-PLATFORM blacklist 
34.69.117.62 GOOGLE blacklist 
34.70.123.227 GOOGLE blacklist 
34.70.37.227 GOOGLE blacklist 
35.184.95.72 GOOGLE blacklist 
35.192.135.139 GOOGLE blacklist 
35.192.5.156 GOOGLE blacklist 
35.202.176.239 GOOGLE blacklist 
35.208.121.216 GOOGLE blacklist 
35.206.105.37 GOOGLE blacklist 
35.208.244.18 GOOGLE blacklist 
35.208.10.124 GOOGLE blacklist 
35.209.67.207 GOOGLE blacklist 
35.222.126.238 GOOGLE blacklist 
35.223.167.9 GOOGLE blacklist 
35.225.203.128 GOOGLE blacklist 
35.232.122.203 GOOGLE blacklist 
35.232.58.54 GOOGLE blacklist 
35.238.96.225 GOOGLE blacklist 
146.66.121.0/24
GOOGLE-CLOUD-PLATFORM blacklist 
146.66.122.0/24
GOOGLE-CLOUD-PLATFORM blacklist 
35.206.120.11 GOOGLE blacklist 
35.225.161.143 GOOGLE blacklist 
104.197.42.21 GOOGLE blacklist 
35.224.11.180 GOOGLE blacklist 
35.209.140.34 GOOGLE blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: fvhh.net

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

35.209.140.34

Additional external SPF records

We could find other records authorized in the SPF record

include:us._netblocks.mimecast.com
v=spf1 ip4:207.211.31.0/25 ip4:205.139.110.0/24 ip4:216.205.24.0/24 ip4:170.10.151.0/24 ip4:170.10.153.0/24 ip4:170.10.129.0/24 ip4:63.128.21.0/24 ip4:170.10.133.0/24 ip4:185.58.84.93/32 ip4:207.211.41.113/32 ip4:207.211.30.64/26 ip4:207.211.30.128/25 ~all
ipv4:
207.211.31.0/25
ipv4:
205.139.110.0/24
ipv4:
216.205.24.0/24
ipv4:
170.10.151.0/24
ipv4:
170.10.153.0/24
ipv4:
170.10.129.0/24
ipv4:
63.128.21.0/24
ipv4:
170.10.133.0/24
ipv4:
185.58.84.93/32
ipv4:
207.211.41.113/32
ipv4:
207.211.30.64/26
ipv4:
207.211.30.128/25
include:_spf.elasticemail.com
v=spf1 ip4:176.31.7.0/25 ip4:178.33.84.64/27 ip4:51.178.153.0/24 ip4:174.142.128.32/27 ip4:5.135.241.64/26 ip4:5.135.31.128/27 ip4:188.165.95.224/27 ip4:176.31.140.80/28 include:_spf2.elasticemail.com include:_spf3.elasticemail.com ~all
ipv4:
176.31.7.0/25
ipv4:
178.33.84.64/27
ipv4:
51.178.153.0/24
ipv4:
174.142.128.32/27
ipv4:
5.135.241.64/26
ipv4:
5.135.31.128/27
ipv4:
188.165.95.224/27
ipv4:
176.31.140.80/28
include:_spf2.elasticemail.com
v=spf1 ip4:176.31.69.160/28 ip4:176.31.145.240/28 ip4:188.165.144.128/28 ip4:37.59.169.64/28 ip4:37.59.131.32/28 ip4:198.50.170.32/28 ip4:178.33.9.160/28 ip4:51.222.89.0/24 ip4:96.45.68.0/24 ip4:162.254.227.0/24 ip4:46.105.146.0/25 ~all
ipv4:
176.31.69.160/28
ipv4:
176.31.145.240/28
ipv4:
188.165.144.128/28
ipv4:
37.59.169.64/28
ipv4:
37.59.131.32/28
ipv4:
198.50.170.32/28
ipv4:
178.33.9.160/28
ipv4:
51.222.89.0/24
ipv4:
96.45.68.0/24
ipv4:
162.254.227.0/24
ipv4:
46.105.146.0/25
include:_spf3.elasticemail.com
v=spf1 ip4:5.196.146.128/25 ip4:192.99.26.0/25 ip4:104.243.65.0/25 ip4:51.254.70.0/26 ip4:67.227.85.0/24 ip4:67.227.87.0/24 ip4:178.33.242.0/24 ip4:216.169.98.0/23 ip4:217.182.181.0/24 ip4:54.36.22.0/24 ip4:51.38.210.0/24 ip4:142.44.153.0/24 ~all
ipv4:
5.196.146.128/25
ipv4:
192.99.26.0/25
ipv4:
104.243.65.0/25
ipv4:
51.254.70.0/26
ipv4:
67.227.85.0/24
ipv4:
67.227.87.0/24
ipv4:
178.33.242.0/24
ipv4:
216.169.98.0/23
ipv4:
217.182.181.0/24
ipv4:
54.36.22.0/24
ipv4:
51.38.210.0/24
ipv4:
142.44.153.0/24
include:_spf.mailspamprotection.com
v=spf1 include:_nb1.mailspamprotection.com include:_nb2.mailspamprotection.com include:_nb3.mailspamprotection.com ~all
include:_nb1.mailspamprotection.com
v=spf1 ip4:104.154.162.117 ip4:104.197.223.236 ip4:34.66.115.54 ip4:34.69.117.62 ip4:34.70.123.227 ip4:34.70.37.227 ip4:35.184.95.72 ip4:35.192.135.139 ip4:35.192.5.156 ip4:35.202.176.239 ~all
ipv4:
104.154.162.117
ipv4:
104.197.223.236
ipv4:
34.66.115.54
ipv4:
34.69.117.62
ipv4:
34.70.123.227
ipv4:
34.70.37.227
ipv4:
35.184.95.72
ipv4:
35.192.135.139
ipv4:
35.192.5.156
ipv4:
35.202.176.239
include:_nb2.mailspamprotection.com
v=spf1 ip4:35.208.121.216 ip4:35.206.105.37 ip4:35.208.244.18 ip4:35.208.10.124 ip4:35.209.67.207 ip4:35.222.126.238 ip4:35.223.167.9 ip4:35.225.203.128 ip4:35.232.122.203 ip4:35.232.58.54 ~all
ipv4:
35.208.121.216
ipv4:
35.206.105.37
ipv4:
35.208.244.18
ipv4:
35.208.10.124
ipv4:
35.209.67.207
ipv4:
35.222.126.238
ipv4:
35.223.167.9
ipv4:
35.225.203.128
ipv4:
35.232.122.203
ipv4:
35.232.58.54
include:_nb3.mailspamprotection.com
v=spf1 ip4:35.238.96.225 ip4:146.66.121.0/24 ip4:146.66.122.0/24 ip4:35.206.120.11 ip4:35.225.161.143 ip4:104.197.42.21 ip4:35.224.11.180 ~all
ipv4:
35.238.96.225
ipv4:
146.66.121.0/24
ipv4:
146.66.122.0/24
ipv4:
35.206.120.11
ipv4:
35.225.161.143
ipv4:
104.197.42.21
ipv4:
35.224.11.180

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

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.

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.

How secure are your domains and where are the dangers lurking?

Domain risks are often underestimated

A current study by BITKOM reports on the alarming increase in cyber attacks on German companies, the ICANN warns of attacks on the global domain name system and the Federal Office for Information Security (BSI) sees significant risk potential in dealing with domain name. Unfortunately, these risks come into play every day, although this damage could have been prevented.

What should companies know and what can they do?

Practical and with many examples, the over 20-page eBook deals with the basics of domain risk management, specifies legal obligations and deals with responsibilities and liability issues. Numerous domain risks (e.g. "Domain Hijacking") are clearly described and the risk assessment and possible consequences are discussed.

Checklist: What about my own domain risks?

The Risk Atlas supports domain managers to get a first impression of their own risk potential in the company. The checklist includes 53 questions on 14 risk areas and enables a quick introduction to the topic.

⮩ Secure white paper "Domain Risk Management" for free

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:

155.150.208.35.bc.googleusercontent.com

© 2012 - 2021 nicmanager.com