codinggear.blog Codinggear.blog

   
CodingGear | Python, Django, FastAPI Tutorials

Domain Summary

What is the traffic rank for Codinggear.blog?

• Codinggear.blog ranks #2,975,033 globally on HypeStat.

What percent of global Internet users visit Codinggear.blog?

• 4.77E-5% of global Internet users visit Codinggear.blog

How many people visit Codinggear.blog each day?

• Codinggear.blog receives approximately 2.4K visitors and 1,939 page impressions per day.

Which countries does Codinggear.blog receive most of its visitors from?

• Codinggear.blog is mostly visited by people located in India,United States,Russian Federation.

How much Codinggear.blog can earn?

• Codinggear.blog should earn about $6.42/day from advertising revenue.

What is Codinggear.blog estimated value?

• Estimated value of Codinggear.blog is $5,958.05.

What IP addresses does Codinggear.blog resolve to?

• Codinggear.blog resolves to the IP addresses 2600:1f11:f39:6f3f:ad82:13e1:7fed:7818, 15.222.186.137.

Where are Codinggear.blog servers located in?

• Codinggear.blog has servers located in Montreal, Quebec, H3H, Canada.

codinggear.blog Profile

Title:CodingGear | Python, Django, FastAPI Tutorials
Description:Python, Django, FastAPI Tutorials
Category:Computers Electronics and Technology / Programming and Developer Software
Edit Site Info

What technologies does codinggear.blog use?

These are the technologies used at codinggear.blog. codinggear.blog has a total of 19 technologies installed in 16 different categories.
Cookie compliance
Funding Choices Funding Choices
Advertising
Google AdSense Google AdSense
Analytics
Google Analytics Google Analytics
Site Kit Site Kit
Security
HSTS HSTS
JavaScript Libraries
jQuery jQuery
jQuery Migrate jQuery Migrate
Slick Slick
Web Servers
LiteSpeed LiteSpeed
Caching
Litespeed Cache Litespeed Cache
WordPress plugins
Litespeed Cache Litespeed Cache
RankMath SEO RankMath SEO
Site Kit Site Kit
Spectra Spectra
Gutenberg Gutenberg
Miscellaneous
Open Graph Open Graph
Prism Prism
SEO
RankMath SEO RankMath SEO
CMS
WordPress WordPress
Blogs
WordPress WordPress
WordPress themes
Zakra Zakra
Editors
Gutenberg Gutenberg
Programming Languages
PHP PHP
Databases
MySQL MySQL

codinggear.blog Traffic Analysis

Codinggear.blog is ranked #2,975,033 in the world. This website is viewed by an estimated 2.4K visitors daily, generating a total of 1.9K pageviews. This equates to about 71.2K monthly visitors. Codinggear.blog traffic has decreased by 15.58% compared to last month.
Daily Visitors2.4K
4.65%
Monthly Visits71.2K
15.58%
Pages per Visit0.82
1.26%
Visit duration00:59
126.92%
Bounce Rate28.84%
2.34%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
2,350
Monthly Visits:
71,205
Pages per Visit:
0.82
Daily Pageviews:
1,939
Avg. visit duration:
00:59
Bounce rate:
28.84%
Global Reach:
4.77E-5%
Monthly Visits (SEMrush):
17,996
Monthly Unique Visitors (SEMrush):
15,580
Monthly Visits (SimilarWeb):
71,950
HypeRank:
2,975,033
SEMrush Rank:
1,185,439
SimilarWeb Rank:
1,502,640
*All traffic values are estimates only.

Traffic sources

Direct:
2.69%
Referral:
1.42%
Search:
95.89%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

70.5K
JUL
84.3K
AUG
71.2K
SEP

Visitors by country

Country
Users%
 
India 13.68%
 
United States 9.22%
 
Russian Federation 3.70%
 
Turkey 2.96%
 
Azerbaijan 2.15%

Which sites are competitors to codinggear.blog?

Websites similar to codinggear.blog 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 408 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with codinggear.blog 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:
123

  ▼

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:
  codinggear.blog
Rank:
(Rank based on keywords, cost and organic traffic)
  1,185,439
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,535
Organic Traffic:
(Number of visitors coming from top 20 search results)
  656
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $342.00
Full SEMrush Report >>

Revenue report ▼

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

How much would codinggear.blog make?

Daily Revenue:
$6.42
Monthly Revenue:
$192.60
Yearly Revenue:
$2,343.30
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 179$0.86
 
India 265$0.10
 
Russian Federation 72$0.03
 
Azerbaijan 42$0.01
 
Turkey 57$0.01

Loss of money due to Adblock?

Daily Revenue Loss:
$0.19
Monthly Revenue Loss:
$5.65
Yearly Revenue Loss:
$68.79
Daily Pageviews Blocked:
121
Monthly Pageviews Blocked:
3,643
Yearly Pageviews Blocked:
44,319

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 32$0.16
 
India 74$0.03
 
Azerbaijan 7$0.00
 
Russian Federation 4$0.00
 
Turkey 4$0.00

How much is codinggear.blog worth?

Website Value:
$6K

Ad Experience Report ▼

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

Mobile summary

Root domain:
codinggear.blog
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:
codinggear.blog
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:
codinggear.blog
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 codinggear.blog hosted? ▼

Codinggear.blog may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2600:1f11:f39:6f3f:ad82:13e1:7fed:7818, 15.222.186.137
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Montreal
Quebec, QC
H3H
Canada, CA
 

Other sites hosted on 15.222.186.137

How fast does codinggear.blog load? ▼

The average loading time of codinggear.blog is 253 ms. The Desktop speed index is 96 and mobile speed index is 76.
Average Load Time:
253 ms

Page Speed (Google PageSpeed Insights) - Desktop

96
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)4ms 89% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 89% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)1.4s 48% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 48% 36% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 36% 15% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 15%
First Contentful Paint (FCP)2.2s 65% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 65% 19% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 19% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
First Input Delay (FID)4ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)82ms 89% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 89% 6% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 6% 3% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 3%
Largest Contentful Paint (LCP)2.5s 75% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 75% 13% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 13% 11% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 11%

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)4ms 89% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 89% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)1.4s 48% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 48% 36% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 36% 15% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 15%
First Contentful Paint (FCP)2.2s 65% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 65% 19% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 19% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
First Input Delay (FID)4ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)82ms 89% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 89% 6% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 6% 3% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 3%
Largest Contentful Paint (LCP)2.5s 75% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 75% 13% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 13% 11% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 11%

Lab Data

Max Potential First Input Delay 80 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
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
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
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
Total Blocking Time 60 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 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 1.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
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
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 2.3 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
Largest Contentful Paint 1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful 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

Page Speed (Google PageSpeed Insights) - Mobile

76
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)1ms 89% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 93% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)2.1s 48% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 29% 40% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 40% 30% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 30%
First Contentful Paint (FCP)3.2s 65% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 43% 29% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 29% 26% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 26%
First Input Delay (FID)25ms 89% of loads for this page have a fast (<100ms) First Input Delay (FID) 89% 7% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 7% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%
Interactive To Next Paint (INP)231ms 89% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 70% 21% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 21% 7% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 7%
Largest Contentful Paint (LCP)3.4s 75% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 60% 21% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 21% 17% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 17%

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 93% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 93% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)2.1s 29% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 29% 40% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 40% 30% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 30%
First Contentful Paint (FCP)3.2s 43% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 43% 29% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 29% 26% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 26%
First Input Delay (FID)25ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 89% 7% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 7% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%
Interactive To Next Paint (INP)231ms 70% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 70% 21% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 21% 7% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 7%
Largest Contentful Paint (LCP)3.4s 60% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 60% 21% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 21% 17% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 17%

Lab Data

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
Total Blocking Time 800 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
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
Max Potential First Input Delay 290 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
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
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
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Time to Interactive 5.6 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
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
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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets

Does codinggear.blog 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 codinggear.blog are reduced by 76%.
codinggear.blog use br compression.
Original size: 119.68 KB
Compressed size: 27.7 KB
File reduced by: 91.98 KB (76%)

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. codinggear.blog supports HTTPS.
 codinggear.blog supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: codinggear.blog
Organization:
Location:
Issuer: R3
Valid from: Oct 12 18:48:08 2023 GMT
Valid until: Jan 10 18:48:07 2024 GMT
Authority: CA:FALSE
Keysize:
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.
 codinggear.blog 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: max-age=2592000, private, s-maxage=0, proxy-revalidate
content-encoding: br
content-type: text/html; charset=UTF-8
date: Tue, 31 Oct 2023 19:49:01 UTC
display: pub_site_to_orig_sol
link: <https://codinggear.blog/wp-json/>; rel="https://api.w.org/"
pagespeed: off
referrer-policy: no-referrer-when-downgrade
response: 200
server: LiteSpeed
set-cookie: ezoadgid_370542=-1; Path=/; Domain=codinggear.blog; Expires=Tue, 31 Oct 2023 20:19:01 UTC
set-cookie: ezoref_370542=hypestat.com; Path=/; Domain=codinggear.blog; Expires=Tue, 31 Oct 2023 21:49:01 UTC
set-cookie: ezosuibasgeneris-1=f95ebf8b-2ae4-4e32-53d4-c8f91c400c3c; Path=/; Domain=codinggear.blog; Expires=Wed, 30 Oct 2024 19:49:01 UTC; Secure; SameSite=None
set-cookie: ezoab_370542=mod220; Path=/; Domain=codinggear.blog; Expires=Tue, 31 Oct 2023 21:49:01 UTC
set-cookie: active_template::370542=pub_site.1698781741; Path=/; Domain=codinggear.blog; Expires=Thu, 02 Nov 2023 19:49:01 UTC
set-cookie: ezopvc_370542=1; Path=/; Domain=codinggear.blog; Expires=Tue, 31 Oct 2023 20:19:01 UTC
set-cookie: lp_370542=https://codinggear.blog/; Path=/; Domain=codinggear.blog; Expires=Tue, 31 Oct 2023 20:19:01 UTC
set-cookie: ezovuuidtime_370542=1698781741; Path=/; Domain=codinggear.blog; Expires=Thu, 02 Nov 2023 19:49:01 UTC
set-cookie: ezovuuid_370542=2ff4808d-4956-4af7-7b89-248503e21410; Path=/; Domain=codinggear.blog; Expires=Tue, 31 Oct 2023 20:19:01 UTC
strict-transport-security: max-age=31536000; includeSubDomains; preload;
vary: Accept-Encoding,User-Agent
x-content-type-options: nosniff
x-ez-proxy-out: true 2.4
x-ezoic-cdn: Hit ds;mm;aa8aa30eff65724405adc2e16e4326c9;2-370542-159;c61ce143-f200-4762-5188-c447b28329a3
x-frame-options: SAMEORIGIN
x-middleton-display: pub_site_to_orig_sol
x-middleton-response: 200
x-origin-cache-control: 
x-sol: pub_site
x-turbo-charged-by: LiteSpeed
x-xss-protection: 1; mode=block

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 v=spf1 +a +mx +ip4:198.187.29.24 include:spf.web-hosting.com ~all 1200
MX mx2-hosting.jellyfish.systems 1200
MX mx1-hosting.jellyfish.systems 1200
MX mx3-hosting.jellyfish.systems 1200
SOA 900
Mname coral.ezoicns.com
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
AAAA 2600:1f11:f39:6f3e:f152:7be7:8f54:a226 60
AAAA 2600:1f11:f39:6f3f:ad82:13e1:7fed:7818 60
A 3.98.12.230 60
A 15.222.186.137 60
NS coral.ezoicns.com 3469
NS horse.ezoicns.com 3469
NS human.ezoicns.com 3469
NS moose.ezoicns.com 3469

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 May 2, 2022 and will expire on May 2, 2024 if not renewed. This website is now assigned through the registrar Namecheap. The WHOIS data for this website's domain was last updated on August 31, 2023.
Domain Created:
2022-05-02
Domain Expires:
2024-05-02
Domain Updated:
2023-08-31
Domain Age:
2 years 7 months 10 days
Domain Registrar:
Namecheap
Domain Owner:
Privacy service provided by Withheld for Privacy e
WhoIs:
 

Domain Name: CODINGGEAR.BLOG
Registry Domain ID: D294947384-CNIC
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: https://namecheap.com
Updated Date: 2023-08-31T16:56:11.0Z
Creation Date: 2022-05-02T16:23:58.0Z
Registry Expiry Date: 2024-05-02T23:59:59.0Z
Registrar: Namecheap
Registrar IANA ID: 1068
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant State/Province: Capital Region
Registrant Country: IS
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: CORAL.EZOICNS.COM
Name Server: HORSE.EZOICNS.COM
DNSSEC: unsigned
Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.9854014545
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-10-31T19:50:11.0Z > IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit
https://www.centralnic.com/support/rdap