vitaldata.com.br Vitaldata.com.br

   
VitalData - Soluções em Dados

Domain Summary

What is the traffic rank for Vitaldata.com.br?

• Vitaldata.com.br ranks #1,841,759 globally on HypeStat.

What percent of global Internet users visit Vitaldata.com.br?

• 1.45E-5% of global Internet users visit Vitaldata.com.br

How many people visit Vitaldata.com.br each day?

• Vitaldata.com.br receives approximately 716 visitors and 987 page impressions per day.

Which countries does Vitaldata.com.br receive most of its visitors from?

• Vitaldata.com.br is mostly visited by people located in Brazil.

How much Vitaldata.com.br can earn?

• Vitaldata.com.br should earn about $1.31/day from advertising revenue.

What is Vitaldata.com.br estimated value?

• Estimated value of Vitaldata.com.br is $1,258.01.

What IP addresses does Vitaldata.com.br resolve to?

• Vitaldata.com.br resolves to the IP addresses 2a02:4780:1:571::d67:7054:1, 31.170.160.66.

Where are Vitaldata.com.br servers located in?

• Vitaldata.com.br has servers located in Asheville, North Carolina, 28801, United States.

vitaldata.com.br Profile

Title:VitalData - Soluções em Dados
Edit Site Info

What technologies does vitaldata.com.br use?

These are the technologies used at vitaldata.com.br. vitaldata.com.br has a total of 4 technologies installed in 4 different categories.
Miscellaneous
HTTP/3 HTTP/3
Hosting
Hostinger Hostinger
Web Servers
LiteSpeed LiteSpeed
Programming Languages
PHP PHP

vitaldata.com.br Traffic Analysis

Vitaldata.com.br is ranked #1,841,759 in the world. This website is viewed by an estimated 716 visitors daily, generating a total of 1K pageviews. This equates to about 21.7K monthly visitors.
Daily Visitors716
Monthly Visits21.7K
Pages per Visit1.38
Visit duration01:32
Bounce Rate76.78%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
716
Monthly Visits:
21,695
Pages per Visit:
1.38
Daily Pageviews:
987
Avg. visit duration:
01:32
Bounce rate:
76.78%
Global Reach:
1.45E-5%
Monthly Visits (SimilarWeb):
21,050
HypeRank:
1,841,759
SEMrush Rank:
25,619,432
SimilarWeb Rank:
1,841,759
*All traffic values are estimates only.

Total Visits Last 3 Months

26.4K
DEC
21.7K
JAN
21.7K
FEB

Visitors by country

Country
Users%
 
Brazil 100.00%
Last update was 80 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with vitaldata.com.br in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
32

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  vitaldata.com.br
Rank:
(Rank based on keywords, cost and organic traffic)
  25,619,432
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  2
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $1.3 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $39.3 and annual gross revenue of approximately $478.2. Based on these figures, the site's net worth is estimated at around $1.3K.

How much would vitaldata.com.br make?

Daily Revenue:
$1.31
Monthly Revenue:
$39.30
Yearly Revenue:
$478.15
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Brazil 987$1.31

Loss of money due to Adblock?

Daily Revenue Loss:
$0.08
Monthly Revenue Loss:
$2.36
Yearly Revenue Loss:
$28.75
Daily Pageviews Blocked:
59
Monthly Pageviews Blocked:
1,777
Yearly Pageviews Blocked:
21,615

Daily revenue loss by country

 
CountryBlockedLost Money
 
Brazil 59$0.08

How much is vitaldata.com.br worth?

Website Value:
$1.3K

Ad Experience Report ▼

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

Mobile summary

Root domain:
vitaldata.com.br
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
vitaldata.com.br
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
vitaldata.com.br
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is vitaldata.com.br hosted? ▼

Vitaldata.com.br may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2a02:4780:1:571::d67:7054:1, 31.170.160.66
ASN:
AS47583 
ISP:
Hostinger International Limited 
Server Location:
Asheville
North Carolina, NC
28801
United States, US
 

Other sites hosted on 31.170.160.66

How fast does vitaldata.com.br load? ▼

The average loading time of vitaldata.com.br is 194 ms. The Desktop speed index is 100 and mobile speed index is 100.
Average Load Time:
194 ms

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an 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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Lab Data

Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
First Contentful Paint 0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Minimize third-party usage  
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 how to minimize third-party impact
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Largest Contentful Paint 0.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Time to Interactive 0.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Speed Index 0.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an 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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s)Largest Contentful Paint (LCP) 0%

Lab Data

Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Minimize third-party usage  
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 how to minimize third-party impact
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Time to Interactive 0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric

Does vitaldata.com.br use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on vitaldata.com.br are reduced by 41%.
vitaldata.com.br use br compression.
Original size: 1.06 KB
Compressed size: 632 B
File reduced by: 457 B (41%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  SAFE

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. vitaldata.com.br supports HTTPS.
 vitaldata.com.br supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: vitaldata.com.br
Organization:
Location:
Issuer: R11
Valid from: Mar 26 18:45:17 2025 GMT
Valid until: Jun 24 18:45:16 2025 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: R11
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 vitaldata.com.br supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
x-powered-by: PHP/7.4.33
content-type: text/html; charset=UTF-8
content-length: 632
content-encoding: br
vary: Accept-Encoding
date: Wed, 02 Apr 2025 01:31:22 GMT
server: LiteSpeed
platform: hostinger
panel: hpanel
content-security-policy: upgrade-insecure-requests
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
SOA 86400
Mname ns1.hostinger.com.br
Rname dns.hostinger.com
Serial Number 2019082703
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 86400
TXT v=spf1 include:_spf.mail.hostinger.com ~all 14400
TXT google-site-verification=GNTBhihsRV0IBNWDmvKOuCTMOhXJvrbXjdFHkHfWH0M 14400
MX mx1.hostinger.com 14400
MX mx2.hostinger.com 14400
AAAA 2a02:4780:1:571::d67:7054:1 14365
A 31.170.160.66 1764
NS ns1.hostinger.com.br 3564
NS ns2.hostinger.com.br 3564
NS ns3.hostinger.com.br 3564
NS ns4.hostinger.com.br 3564
CAA comodoca.com 14400
CAA globalsign.com 14400
CAA pki.goog 14400
CAA comodoca.com 14400
CAA letsencrypt.org 14400
CAA letsencrypt.org 14400
CAA digicert.com 14400
CAA digicert.com 14400
CAA globalsign.com 14400
CAA pki.goog 14400

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on June 6, 2018 and will expire on June 6, 2025 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on June 8, 2024.
Domain Created:
2018-06-06
Domain Expires:
2025-06-06
Domain Updated:
2024-06-08
Domain Age:
7 years 15 days
Domain Owner:
Alisson Rodrigo
WhoIs:
 

% Copyright (c) Nic.br - Use of this data is governed by the Use and
% Privacy Policy at https://registro.br/upp . Distribution,
% commercialization, reproduction, and use for advertising or similar
% purposes are expressly prohibited.
% 2025-04-01T22:31:56-03:00 - 108.178.0.234

domain:      vitaldata.com.br
owner:       Alisson Rodrigo
ownerid:     ***.170.104-**
country:     BR
owner-c:     ALROD623
tech-c:      ALROD623
nserver:     ns1.hostinger.com.br
nsstat:      20250331 AA
nslastaa:    20250331
nserver:     ns2.hostinger.com.br
nsstat:      20250331 AA
nslastaa:    20250331
nserver:     ns3.hostinger.com.br
nsstat:      20250331 AA
nslastaa:    20250331
nserver:     ns4.hostinger.com.br
nsstat:      20250331 AA
nslastaa:    20250331
saci:        yes
created:     20180606 #18441508
changed:     20240608
expires:     20250606
status:      published
provider:    WEBLINK (102)

nic-hdl-br:  ALROD623
person:      Alisson Rodrigo
e-mail:      email
country:     BR
created:     20180606
changed:     20180606

% Security and mail abuse issues should also be addressed to cert.br,
% respectivelly to email and email
%
% whois.registro.br only accepts exact match queries for domains,
% registrants, contacts, tickets, providers, IPs, and ASNs.