Viajantecurioso.Com.Br - Info receives about 3,629 unique visitors and 3,629 (1.00 per visitor) page views per day which should earn about $14.81/day from advertising revenue. Estimated site value is $10,808.61. According to Alexa Traffic Rank is ranked number 725,719 in the world and 8.0E-5% of global Internet users visit it. Site is hosted in United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Font Scripts
Font Awesome
Google Font API
Google AdSense
Google Analytics
W3 Total Cache
Programming Languages
MySQL Profile

Title: Viajante Curioso - Despertando o Espírito Viajante que existe em você
Description: Despertando o Espírito Viajante que existe em você
Last update was 137 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

3.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
725,719 visit alexa
Alexa Reach:
8.0E-5%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Cloudflare Inc 
Server Location:

United States, US

Other sites hosted on

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)3.0s % of loads for this page have a fast (<1s) First Contentful Paint (FCP) 17% 57% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 57% 25% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 25%
First Input Delay (FID)441ms 78% of loads for this page have a fast (<100ms) First Input Delay (FID) 78% 12% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 12% 8% of loads for this page have a slow (>300ms) First Input Delay (FID) 8%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)3.0s 17% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 17% 57% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 57% 25% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 25%
First Input Delay (FID)441ms % of loads for this page have a fast (<100ms) First Input Delay (FID) 78% 12% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 12% 8% of loads for this page have a slow (>300ms) First Input Delay (FID) 8%

Lab Data

Estimated Input Latency 120 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 5617 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 1,060 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 9.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 4.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 340 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 10.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Reduce the impact of third-party code - Third-party code blocked the main thread for 1,200 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

SizeMain-Thread Blocking Time
600 KB828 ms
61 KB234 ms
20 KB136 ms
10 KB0 ms
9 KB0 ms
5 KB0 ms
2 KB0 ms
2 KB0 ms
1 KB0 ms
1 KB0 ms
1 KB0 ms
1 KB0 ms
0 KB0 ms
0 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
500 ms
8 ms
972 ms
6 ms
978 ms
78 ms
1060 ms
28 ms
1089 ms
34 ms
1129 ms
54 ms
1187 ms
50 ms
1237 ms
9 ms
1254 ms
6 ms
1272 ms
52 ms
1336 ms
41 ms
1548 ms
11 ms
1562 ms
7 ms
1569 ms
5 ms
1574 ms
36 ms
1617 ms
7 ms
1626 ms
36 ms
1663 ms
9 ms
1678 ms
23 ms
1715 ms
8 ms
1747 ms
53 ms
1806 ms
20 ms
1838 ms
156 ms
1994 ms
14 ms
2009 ms
10 ms
2019 ms
8 ms
2035 ms
6 ms
2057 ms
41 ms
2098 ms
10 ms
2108 ms
54 ms
2260 ms
8 ms
2377 ms
6 ms
2410 ms
8 ms
2462 ms
6 ms
2486 ms
14 ms
2504 ms
11 ms
2516 ms
21 ms
2541 ms
9 ms
2568 ms
31 ms
2598 ms
7 ms
2614 ms
13 ms
2644 ms
6 ms
2867 ms
12 ms
2890 ms
84 ms
3999 ms
21 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
4 ms
157 ms
5 ms
4 ms
Reduce JavaScript execution time - 3.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
1783 ms131 ms22 ms
601 ms359 ms11 ms
589 ms528 ms45 ms
537 ms476 ms37 ms
351 ms342 ms9 ms
314 ms270 ms6 ms
241 ms225 ms13 ms
230 ms201 ms29 ms
214 ms177 ms18 ms
188 ms56 ms18 ms
185 ms176 ms8 ms
162 ms91 ms7 ms
132 ms119 ms7 ms
73 ms53 ms5 ms
Remove unused CSS - Potential savings of 33 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
35 KB33 KB
Avoids enormous network payloads - Total size was 939 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

90 KB
90 KB
59 KB
56 KB
55 KB
38 KB
35 KB
34 KB
33 KB
30 KB
Minimize main-thread work - 5.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
3414 ms
797 ms
Style & Layout
664 ms
Script Parsing & Compilation
317 ms
261 ms
Parse HTML & CSS
255 ms
Garbage Collection
188 ms
Avoid an excessive DOM size - 1,759 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 94 requests • 953 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
94953 KB
36665 KB
23106 KB
662 KB
557 KB
443 KB
2019 KB
00 KB
86779 KB
Eliminate render-blocking resources - Potential savings of 890 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
35 KB1230
2 KB780
5 KB930
33 KB1380
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms216 ms0 KB0 KB301
217 ms474 ms19 KB101 KB200text/htmlDocument
490 ms948 ms35 KB147 KB200text/cssStylesheet
490 ms501 ms2 KB26 KB200text/cssStylesheet
490 ms508 ms5 KB22 KB200text/cssStylesheet
491 ms538 ms33 KB95 KB200application/x-javascriptScript
491 ms505 ms38 KB103 KB200text/javascriptScript,ret_img,w_600/
491 ms669 ms1 KB0 KB307text/html
506 ms1566 ms2 KB4 KB200application/javascriptScript
690 ms1781 ms11 KB43 KB200application/javascriptScript
1063 ms1367 ms56 KB271 KB200application/x-javascriptScript
669 ms689 ms18 KB18 KB200image/pngImage
1063 ms1419 ms5 KB14 KB200application/x-javascriptScript
1063 ms1089 ms26 KB79 KB200application/javascriptScript
1063 ms1069 ms18 KB43 KB200text/javascriptScript
1074 ms1077 ms9 KB9 KB200font/woff2Font
1075 ms1232 ms8 KB7 KB200application/font-woffFont
1082 ms1103 ms14 KB14 KB200application/x-font-woffFont
1126 ms1133 ms1 KB0 KB200application/javascriptScript
1129 ms1158 ms90 KB240 KB200text/javascriptScript
1144 ms1170 ms90 KB240 KB200text/javascriptScript
1163 ms1170 ms7 KB15 KB200text/htmlDocument
1214 ms1221 ms1 KB0 KB200image/gifImage
1214 ms1218 ms1 KB0 KB200image/gifImage
1214 ms1239 ms1 KB0 KB302text/html
1239 ms1244 ms1 KB0 KB200image/gifImage
1299 ms1522 ms7 KB22 KB200text/htmlDocument
1300 ms1308 ms30 KB78 KB200text/javascriptScript
1549 ms1576 ms55 KB153 KB200text/javascriptScript
1596 ms1689 ms16 KB50 KB200text/javascriptScript
1614 ms1619 ms17 KB17 KB200font/woff2Font
1616 ms1620 ms10 KB9 KB200font/woff2Font
1700 ms1711 ms59 KB159 KB200text/javascriptScript
1772 ms1878 ms1 KB0 KB200text/plainXHR
1774 ms1791 ms25 KB65 KB200text/javascriptScript
1776 ms1780 ms4 KB0 KB200text/htmlOther
1801 ms1801 ms0 KB8 KB200image/svg+xmlImage
1802 ms1802 ms0 KB3 KB200image/pngImage
1929 ms1949 ms2 KB2 KB200text/htmlDocument
1960 ms1960 ms0 KB0 KB200image/gifImage
2005 ms2030 ms34 KB78 KB200application/javascriptScript
2108 ms2215 ms1 KB0 KB200text/javascriptScript
2108 ms2215 ms1 KB0 KB200text/javascriptScript
2109 ms2222 ms1 KB0 KB200text/javascriptScript
2109 ms2217 ms1 KB0 KB200text/javascriptScript
2109 ms2213 ms1 KB0 KB200text/javascriptScript
2110 ms2340 ms1 KB0 KB200text/javascriptScript
2110 ms2218 ms1 KB0 KB200text/javascriptScript
2110 ms2231 ms1 KB0 KB200text/javascriptScript
2111 ms2374 ms1 KB0 KB200text/javascriptScript
2111 ms2216 ms1 KB0 KB200text/javascriptScript
2112 ms2346 ms1 KB0 KB200text/javascriptScript
2135 ms2438 ms26 KB96 KB200text/htmlDocument
2447 ms2453 ms3 KB6 KB200text/javascriptScript
2448 ms2459 ms1 KB5 KB200text/cssStylesheet
2453 ms2459 ms1 KB1 KB200text/javascriptScript
2453 ms2459 ms6 KB13 KB200text/javascriptScript
2454 ms2460 ms12 KB30 KB200text/javascriptScript
2455 ms2460 ms2 KB2 KB200text/javascriptScript
2455 ms2465 ms30 KB76 KB200text/javascriptScript
2455 ms2461 ms6 KB12 KB200text/javascriptScript
2474 ms2703 ms0 KB0 KB204text/htmlImage
2483 ms2520 ms17 KB16 KB200image/jpegImage
2483 ms2517 ms15 KB14 KB200image/jpegImage
2484 ms2571 ms7 KB7 KB200image/jpegImage
2484 ms2659 ms14 KB13 KB200image/jpegImage
2484 ms2654 ms14 KB14 KB200image/jpegImage
2485 ms2550 ms12 KB12 KB200image/jpegImage
2508 ms2519 ms1 KB0 KB200text/htmlFetch
2509 ms2519 ms1 KB0 KB200text/htmlFetch
2510 ms2521 ms1 KB0 KB200text/htmlFetch
2511 ms2518 ms1 KB0 KB200text/htmlFetch
2511 ms2521 ms1 KB0 KB200text/htmlFetch
2512 ms2520 ms1 KB0 KB200text/htmlFetch
2529 ms2538 ms2 KB1 KB200text/htmlDocument
2603 ms2603 ms0 KB0 KB200image/pngImage
2625 ms2709 ms1 KB0 KB200image/gifImage
2625 ms2653 ms1 KB0 KB302text/html
2626 ms2701 ms1 KB0 KB302
2626 ms2668 ms1 KB0 KB302
2626 ms2657 ms1 KB0 KB302text/html
2626 ms2666 ms0 KB0 KB302text/html
2627 ms2770 ms1 KB0 KB302text/html
2627 ms2633 ms1 KB0 KB204text/htmlImage
2653 ms2660 ms1 KB0 KB200image/pngImage
2657 ms2683 ms1 KB0 KB302text/html
2666 ms2690 ms1 KB0 KB200image/pngImage
2668 ms2711 ms1 KB0 KB302
2683 ms2692 ms1 KB0 KB200image/pngImage
2701 ms2707 ms1 KB0 KB200image/pngImage
2711 ms2719 ms1 KB0 KB200image/pngImage
2770 ms2838 ms1 KB0 KB302text/html
2838 ms2844 ms1 KB0 KB200image/pngImage
2860 ms2866 ms6 KB12 KB200text/javascriptScript
Uses efficient cache policy on static assets - 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
7200000 ms18 KB
172800000 ms26 KB
1209600000 ms12 KB
1209600000 ms6 KB
1209600000 ms2 KB
1209600000 ms1 KB
2592000000 ms11 KB
2592000000 ms2 KB
7776000000 ms6 KB
7776000000 ms3 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 9 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 260 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (15 minutes) (50 minutes) (50 minutes) (60 minutes)******ytics.js (2 hours)

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/#facebook" class="a2a_button_facebook">Facebook</a> and 39 others are close to other tap targets.
The tap target <a href="/#twitter" class="a2a_button_twitter">Twitter</a> and 29 others are close to other tap targets.
The tap target <div id="abgc" class="abgc"></div> is close to 1 other tap targets.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 13.4KiB (18% reduction).

Compressing could save 3.6KiB (23% reduction).
Compressing could save 2.6KiB (20% reduction).
Compressing***16242 could save 2.5KiB (19% reduction).
Compressing could save 1.9KiB (17% reduction).
Compressing could save 1.7KiB (12% reduction).
Compressing could save 1.1KiB (17% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use br compression.
Original size: 101.26 KB
Compressed size: 18.02 KB
File reduced by: 83.24 KB (82%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: CloudFlare Inc ECC CA-2
Valid from: Oct 15 00:00:00 2019 GMT
Valid until: Oct 9 12:00:00 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sat, 23 Nov 2019 17:11:03 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: max-age=3600
Expires: Sat, 23 Nov 2019 18:11:03 GMT
X-Content-Type-Options: nosniff
Vary: Accept-Encoding
Server: cloudflare
CF-RAY: 53a4c295dd7dc637-MSP

HTTP/2 200 
date: Sat, 23 Nov 2019 17:11:03 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d255803d7095ac076772933e38a232e8a1574529063; expires=Mon, 23-Dec-19 17:11:03 GMT; path=/;; HttpOnly
last-modified: Sat, 23 Nov 2019 15:36:00 GMT
vary: Accept-Encoding
referrer-policy: no-referrer-when-downgrade
x-turbo-charged-by: LiteSpeed
cf-cache-status: DYNAMIC
x-content-type-options: nosniff
expect-ct: max-age=604800, report-uri=""
server: cloudflare
cf-ray: 53a4c296be4441f9-MSP
content-encoding: br

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
A 266
A 266
NS 3566
NS 3566

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
% Copyright (c)
% The use of the data below is only permitted as described in
% full by the terms of use at ,
% being prohibited its distribution, commercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2019-11-23T14:11:37-03:00

owner: Diego Oliva
owner-c: DIOLI379
admin-c: DIOLI379
tech-c: DIOLI379
billing-c: DIOLI379
nsstat: 20191121 AA
nslastaa: 20191121
nsstat: 20191121 AA
nslastaa: 20191121
saci: yes
created: 20170411 #16872262
changed: 20190424
expires: 20210411
status: published

nic-hdl-br: DIOLI379
person: Diego Oliva
created: 20190130
changed: 20190130

% Security and mail abuse issues should also be addressed to
%, , respectivelly to email
% and email
% accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, contact handle (ID), CIDR block, IP and ASN.
Last update was 137 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
21 secs
22 secs
23 secs
37 secs
1 min
1 min
1 min
2 mins
2 mins
2 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget