usezapay.com.br Usezapay.com.br

   
Consulte e pague os débitos do seu veículo | Zapay

Domain Summary

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

• Usezapay.com.br ranks #430,039 globally on HypeStat.

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

• 0.0008701% of global Internet users visit Usezapay.com.br

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

• Usezapay.com.br receives approximately 42.9K visitors and 125,421 page impressions per day.

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

• Usezapay.com.br is mostly visited by people located in Brazil,Netherlands,Colombia.

How much Usezapay.com.br can earn?

• Usezapay.com.br should earn about $166.77/day from advertising revenue.

What is Usezapay.com.br estimated value?

• Estimated value of Usezapay.com.br is $164,995.08.

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

• Usezapay.com.br resolves to the IP addresses 76.76.21.21.

Where are Usezapay.com.br servers located in?

• Usezapay.com.br has servers located in Walnut, California, 91789, United States.

usezapay.com.br Profile

Title:Consulte e pague os débitos do seu veículo | Zapay
Description:Com a Zapay você pode consultar e pagar o IPVA, multas, licenciamento e DPVAT, com mais rapidez, opções de parcelamento e de qualquer lugar do Brasil.
Tags:
parcelar multas
zapay
parcelar ipva
zapay pagamentos
parcelamento detran
Category:Finance / Other Finance
Edit Site Info

What technologies does usezapay.com.br use?

These are the technologies used at usezapay.com.br. usezapay.com.br has a total of 9 technologies installed in 9 different categories.
Miscellaneous
Amazon S3 Amazon S3
webpack webpack
PaaS
Amazon Web Services Amazon Web Services
Tag Managers
Google Tag Manager Google Tag Manager
Webmail
Google Workspace Google Workspace
Email
Google Workspace Google Workspace
Web Frameworks
Next.js Next.js
Web Servers
Next.js Next.js
Vercel Vercel
JavaScript Frameworks
React React
Programming Languages
Node.js Node.js

usezapay.com.br Traffic Analysis

Usezapay.com.br is ranked #430,039 in the world. This website is viewed by an estimated 42.9K visitors daily, generating a total of 125.4K pageviews. This equates to about 1.3M monthly visitors. Usezapay.com.br traffic has decreased by 51.38% compared to last month.
Daily Visitors42.9K
34.79%
Monthly Visits1.3M
51.38%
Pages per Visit2.92
7.6%
Visit duration03:41
11.6%
Bounce Rate51.86%
8.37%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
42,894
Monthly Visits:
1,299,688
Pages per Visit:
2.92
Daily Pageviews:
125,421
Avg. visit duration:
03:41
Bounce rate:
51.86%
Global Reach:
0.0008701%
Monthly Visits (SEMrush):
965,142
Monthly Unique Visitors (SEMrush):
807,143
Monthly Visits (SimilarWeb):
1,274,092
HypeRank:
430,039
SEMrush Rank:
2,255,453
SimilarWeb Rank:
47,329
*All traffic values are estimates only.

Traffic sources

Direct:
40.67%
Referral:
4.90%
Search:
50.45%
Social:
0.20%
Paid:
3.78%

Desktop vs Mobile

Desktop:
22.58%
Mobile:
77.42%

Total Visits Last 3 Months

1.2M
DEC
2.7M
JAN
1.3M
FEB

Visitors by country

Country
Users%
 
Brazil 99.77%
 
Netherlands 0.11%
 
Colombia 0.09%
 
Portugal 0.03%

Which sites are competitors to usezapay.com.br?

Websites similar to usezapay.com.br are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Last update was 626 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with usezapay.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:
2,410
Bing Index:
110

  ▼

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:
  usezapay.com.br
Rank:
(Rank based on keywords, cost and organic traffic)
  2,255,453
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  735
Organic Traffic:
(Number of visitors coming from top 20 search results)
  237
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $6.00
Full SEMrush Report >>

Revenue report ▼

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

How much would usezapay.com.br make?

Daily Revenue:
$166.77
Monthly Revenue:
$5,003.10
Yearly Revenue:
$60,871.05
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Brazil 125,133$166.43
 
Netherlands 135$0.26
 
Colombia 116$0.08
 
Portugal 37$0.01

Loss of money due to Adblock?

Daily Revenue Loss:
$10.04
Monthly Revenue Loss:
$301.13
Yearly Revenue Loss:
$3,663.71
Daily Pageviews Blocked:
7,548
Monthly Pageviews Blocked:
226,441
Yearly Pageviews Blocked:
2,755,037

Daily revenue loss by country

 
CountryBlockedLost Money
 
Brazil 7,508$9.99
 
Netherlands 23$0.04
 
Colombia 9$0.01
 
Portugal 8$0.00

How much is usezapay.com.br worth?

Website Value:
$165K

Ad Experience Report ▼

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

Mobile summary

Root domain:
usezapay.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:
usezapay.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:
usezapay.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 usezapay.com.br hosted? ▼

Usezapay.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:
76.76.21.21
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Walnut
California, CA
91789
United States, US
 

Other sites hosted on 76.76.21.21

How fast does usezapay.com.br load? ▼

The average loading time of usezapay.com.br is 5255 ms. The Desktop speed index is 75 and mobile speed index is 55.
Average Load Time:
5255 ms

Page Speed (Google PageSpeed Insights) - Desktop

75
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)305ms 93% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 93% 4% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 4% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)971ms 92% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 92% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)16ms 91% of loads for this page have a fast (<100ms) First Input Delay (FID) 91% 4% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 4% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%
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)1.5s 91% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 91% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 3% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 3%

Origin Data

All pages served from this origin have an AVERAGE 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)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)487ms 88% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 88% 8% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 8% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)1.4s 85% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 85% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)14ms 90% of loads for this page have a fast (<100ms) First Input Delay (FID) 90% 4% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 4% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%
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)2.4s 76% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 76% 13% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 13% 9% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 9%

Lab Data

Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
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
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Total Blocking Time 470 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
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 4.1 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
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
Max Potential First Input Delay 380 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
Has 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

Page Speed (Google PageSpeed Insights) - Mobile

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

Cumulative Layout Shift (CLS)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)750ms 93% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 77% 17% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 17% 5% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.4s 92% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 86% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)199ms 64% of loads for this page have a fast (<100ms) First Input Delay (FID) 64% 16% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 16% 18% of loads for this page have a slow (>300ms) First Input Delay (FID) 18%
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)1.5s 91% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 92% 4% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 4% 2% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 2%

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.

Cumulative Layout Shift (CLS)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)871ms 71% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 71% 21% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 21% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.6s 80% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 80% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)186ms 90% of loads for this page have a fast (<100ms) First Input Delay (FID) 66% 15% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 15% 18% of loads for this page have a slow (>300ms) First Input Delay (FID) 18%
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)2.3s 78% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 78% 13% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 13% 8% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 8%

Lab Data

Time to Interactive 18.0 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
Largest Contentful Paint 3.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
First Contentful Paint (3G) 3960 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more about the First Contentful Paint (3G) metric
Speed Index 6.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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
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
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 Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Total Blocking Time 3,180 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
Max Potential First Input Delay 850 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
Has 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
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins

Does usezapay.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 usezapay.com.br are reduced by 85%.
usezapay.com.br use br compression.
Original size: 181.53 KB
Compressed size: 25.89 KB
File reduced by: 155.63 KB (85%)

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. usezapay.com.br has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  51

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. usezapay.com.br supports HTTPS.
 usezapay.com.br supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.usezapay.com.br
Organization:
Location:
Issuer: R3
Valid from: Jan 22 09:27:33 2023 GMT
Valid until: Apr 22 09:27:32 2023 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: ISRG Root X1
Organization: Internet Security Research Group
Location: US
Issuer: DST Root CA X3
Valid from: Jan 20 19:14:03 2021 GMT
Valid until: Sep 30 18:14:03 2024 GMT
Authority: CA:TRUE
Keysize: 4096 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.
 usezapay.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. 
cache-control: public, max-age=0, must-revalidate
content-type: text/plain
date: Tue, 28 Mar 2023 20:59:12 GMT
location: https://www.usezapay.com.br/
refresh: 0;url=https://www.usezapay.com.br/
server: Vercel
strict-transport-security: max-age=63072000
x-vercel-cache: MISS
x-vercel-id: cle1::msrhs-1680037152970-428d26d525c9

HTTP/2 200 
age: 372238
cache-control: public, max-age=0, must-revalidate
content-encoding: br
content-type: text/html; charset=utf-8
date: Fri, 24 Mar 2023 13:35:14 GMT
etag: W/"1vace3gplw3z22"
server: Vercel
strict-transport-security: max-age=63072000
x-matched-path: /
x-powered-by: Next.js
x-vercel-cache: HIT
x-vercel-id: cle1::iad1::c4plg-1680037153082-3fe3f4a792d3

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
TXT google-site-verification=l-QEPaMfEQAUTDa5WP_3lrEwAJjXaBp59oHg8aGYCF4 2
TXT google-site-verification=p2dbplisdjoYkoOB6p9uZrgFEpNh9MOkgj6M4nuuPeI 2
TXT google-site-verification=vTwN-oIVK2DXZ2LlOn8XZZHZUrJd3H524ejFdLWn10k 2
TXT mandrill_verify.c493fx4CxJ46PyQHFyz-QQ 2
TXT postman-domain-verification=7a4716f03fc24399de0afbf3e9445b1982f621de03bfb4ff8217cbe079063df8c9ac4f2d99e79e4a9428592d50715de9d2b130505a0f3ec44150c82e95592436 2
TXT v=spf1 include:spf.binds.co ?all 2
TXT facebook-domain-verification=xkj1o3zlzwct2t3epxawqob60flfpy 2
TXT google-site-verification=FUlFY9aSYLeBSU4KPKRU1gNyYInIro_i5go3CzmUnuA 2
TXT google-site-verification=IyCCvJyBlyO5OkbaYmk7bKxG_bGKF_rGZE6Nj2IF6UY 2
TXT google-site-verification=UTrfcnI0orSG7jxbRDiI3hOWLWa_-NjI7Tu7M0SefIg 2
MX alt1.aspmx.l.google.com 3542
MX alt2.aspmx.l.google.com 3542
MX aspmx.l.google.com 3542
MX alt3.aspmx.l.google.com 3542
MX alt4.aspmx.l.google.com 3542
SOA 842
Mname ns-616.awsdns-13.net
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 76.76.21.21 235
NS ns-115.awsdns-14.com 3535
NS ns-2033.awsdns-62.co.uk 3535
NS ns-616.awsdns-13.net 3535
NS ns-1379.awsdns-44.org 3535

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 July 4, 2017 and will expire on July 4, 2032 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on March 7, 2023.
Domain Created:
2017-07-04
Domain Expires:
2032-07-04
Domain Updated:
2023-03-07
Domain Age:
7 years 5 months 10 days
Domain Owner:
Pedro Henrique Ferreira Vogado
WhoIs:
 

% Copyright (c) Nic.br
%  The use of the data below is only permitted as described in
%  full by the Use and Privacy Policy at https://registro.br/upp ,
%  being prohibited its distribution, commercialization or
%  reproduction, in particular, to use it for advertising or
%  any similar purpose.
%  2023-03-28T18:00:11-03:00 - IP: 67.212.187.106

domain:      usezapay.com.br
owner:       Pedro Henrique Ferreira Vogado
owner-c:     PHFVO2
tech-c:      PHFVO2
nserver:     ns-616.awsdns-13.net
nsstat:      20230326 AA
nslastaa:    20230326
nserver:     ns-115.awsdns-14.com
nsstat:      20230326 AA
nslastaa:    20230326
nserver:     ns-2033.awsdns-62.co.uk
nsstat:      20230326 AA
nslastaa:    20230326
saci:        yes
created:     20170704 #17177481
changed:     20230307
expires:     20320704
status:      published
provider:    UOLHOST (22)

nic-hdl-br:  PHFVO2
person:      Pedro Henrique Ferreira Vogado
created:     20170704
changed:     20210714

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/ , respectivelly to email
% and email
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, CIDR block, IP and ASN.