Let AI power your customer service and lead gen. See how

Is Izito Down?

I have a problem with izito.com.br

Are you having issues? Provide feedback to Izito by selecting the option you are having issues with.

Something else...

Site Online

User reports:
No current problems

User reports 0

izito.com.br problems reported in the last 24 hours

24 hour clock

Most reported problems

Izito.com.br Server Status

Response Header
HTTP headers carry information about the client browser, the requested page and the server status

HTTP/1.1 200 OK
date: Fri, 14 Apr 2023 02:53:58 GMT
Cache-Control: no-cache, no-transform, private
expires: Fri, 14 Apr 2023 02:58:58 GMT
content-type: text/html; charset=UTF-8
accept-ranges: bytes
transfer-encoding: chunked
X-Frame-Options: DENY
Content-Security-Policy: frame-ancestors 'none'

DNS Records
DNS Resource Records associated with a hostname

The DNS is up. We have tried pinging Izito.com.br. There are no DNS Issues detected!

Type	Name	Value	Class	TTL
A	izito.com.br	81.171.31.72	IN	3600
NS	izito.com.br		IN	86400
NS	izito.com.br		IN	86400
NS	izito.com.br		IN	86400
NS	izito.com.br		IN	86400

Safety

HTTPS Encryption

HTTPS Encrypted.

Is Izito safe?

Yes Izito.com.br is Safe according to Google Safe Browsing

Speed

Response Time

The website responded in 0.30 seconds.

Pagesize

The size of the HTML webpage is 8.23 kB.

Text compression

Webpage is Compressed: The filesize is 8.23 kB.

How to Solve Izito.com.br Down or Outage Issues

We have tried pinging Izito.com.br using our servers and the Izito.com.br server responded on time, indicating that there are no current Izito.com.br problems today.

If Izito.com.br is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.

If Izito.com.br is UP for us but you cannot access it, try these solutions:

Do a full Browser refresh of the site holding down CTRL + F5 keys at the same time on your browser
Clear Your browser Cookies and Cache
Fix DNS problems by Clearing your local DNS cache to make sure that you grab the most recent cache that your ISP has