Thekalam.In - Info thekalam.in

thekalam.in receives about 17 unique visitors and 17 (1.00 per visitor) page views per day which should earn about $0.07/day from advertising revenue. Estimated site value is $28.22. According to Alexa Traffic Rank thekalam.in is ranked number 9,763,976 in the world and 1.0E-6% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.27.177.7. This server supports HTTPS and HTTP/2.

About - thekalam.in


Technologies used on Website

Web Servers
Apache
Font Scripts
Google Font API
Programming Languages
PHP
CMS
WordPress
Blogs
WordPress
Databases
MySQL

thekalam.in Profile

Title: Account Suspended
Last update was 168 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is thekalam.in?

17 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
17
Monthly Unique Visitors:
408
Pages per Visit:
1.00
Daily Pageviews:
17
Alexa Rank:
9,763,976 visit alexa
Alexa Reach:
1.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  thekalam.in
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
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
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is thekalam.in?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

Root domain:
thekalam.in
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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

Root domain:
thekalam.in
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

+ How much thekalam.in can earn?

Daily Revenue:
$0.07
Monthly Revenue:
$2.10
Yearly Revenue:
$25.55
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do thekalam.in lose due to Adblock?

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

Daily revenue loss by country

Currently Not Available

How much is thekalam.in worth?

Website Value:
$28.22

+ Where is thekalam.in hosted?

+ How fast does thekalam.in load?

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

Page Speed (Google PageSpeed Insights) - Desktop

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

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.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 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 0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 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 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 9 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
9
Maximum DOM Depth
6
Maximum Child Elements
2
Avoid multiple page redirects - Potential savings of 340 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://thekalam.in/)
0
https://thekalam.in/
190
https://thekalam.in/cgi-sys/suspendedpage.cgi
150
Keep request counts low and transfer sizes small - 7 requests • 54 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
754 KB
Font
138 KB
Stylesheet
19 KB
Document
14 KB
Script
11 KB
Other
21 KB
Image
10 KB
Media
00 KB
Third-party
347 KB
Eliminate render-blocking resources - Potential savings of 70 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.

URL
SizePotential Savings
https://use.fontawesome.com/releases/v5.0.6/css/all.css
9 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://thekalam.in/
0 ms31 ms0 KB0 KB301
https://thekalam.in/
32 ms314 ms1 KB0 KB302text/html
https://thekalam.in/cgi-sys/suspendedpage.cgi
315 ms757 ms4 KB7 KB200text/htmlDocument
https://use.fontawesome.com/releases/v5.0.6/css/all.css
768 ms970 ms9 KB34 KB200text/cssStylesheet
https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
768 ms790 ms1 KB1 KB200application/javascriptScript
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPAAAADqCAMAAACrxjhdAAAAt1BMVEUAAAAAAAD///////////////
978 ms979 ms0 KB3 KB200image/pngImage
https://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2
980 ms997 ms38 KB38 KB200application/font-woff2Font
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000 ms1 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
47 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
783 ms
7 ms
997 ms
7 ms
1004 ms
16 ms
1021 ms
7 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.

URL
Potential Savings
https://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2
17 ms
Remove unused CSS - Potential savings of 9 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.

URL
SizePotential Savings
https://use.fontawesome.com/releases/v5.0.6/css/all.css
9 KB9 KB
Avoids enormous network payloads - Total size was 54 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2
38 KB
https://use.fontawesome.com/releases/v5.0.6/css/all.css
9 KB
https://thekalam.in/cgi-sys/suspendedpage.cgi
4 KB
https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
1 KB
https://thekalam.in/
1 KB
http://thekalam.in/
0 KB
Minimizes main-thread work - 0.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
19 ms
Style & Layout
19 ms
Parse HTML & CSS
4 ms
Script Evaluation
4 ms
Rendering
3 ms
Script Parsing & Compilation
1 ms
Minimize Critical Requests Depth - 3 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 440 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.

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.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. 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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.


Page Speed (Google PageSpeed Insights) - Mobile

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

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.

Lab Data

Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.4 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.4 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 2.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 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 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 4650 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Remove unused CSS - Potential savings of 12 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.

URL
SizePotential Savings
https://use.fontawesome.com/releases/v5.0.6/css/all.css
9 KB9 KB
body { font-family: Arial, Helvetica, sans-serif; font-size: 14px; line-height: 1.428571429; ... } ...
3 KB3 KB
Avoids enormous network payloads - Total size was 54 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2
38 KB
https://use.fontawesome.com/releases/v5.0.6/css/all.css
9 KB
https://thekalam.in/cgi-sys/suspendedpage.cgi
4 KB
https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
1 KB
https://thekalam.in/
1 KB
http://thekalam.in/
0 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
97 ms
Other
82 ms
Parse HTML & CSS
26 ms
Script Evaluation
22 ms
Rendering
7 ms
Script Parsing & Compilation
6 ms
Avoids an excessive DOM size - 9 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
9
Maximum DOM Depth
6
Maximum Child Elements
2
Avoid multiple page redirects - Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://thekalam.in/)
0
https://thekalam.in/
630
https://thekalam.in/cgi-sys/suspendedpage.cgi
480
Keep request counts low and transfer sizes small - 6 requests • 54 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
654 KB
Font
138 KB
Stylesheet
19 KB
Document
14 KB
Script
11 KB
Other
21 KB
Image
00 KB
Media
00 KB
Third-party
247 KB
Eliminate render-blocking resources - Potential savings of 180 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.

URL
SizePotential Savings
https://use.fontawesome.com/releases/v5.0.6/css/all.css
9 KB780
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://thekalam.in/
0 ms54 ms0 KB0 KB301
https://thekalam.in/
55 ms401 ms1 KB0 KB302text/html
https://thekalam.in/cgi-sys/suspendedpage.cgi
401 ms831 ms4 KB7 KB200text/htmlDocument
https://use.fontawesome.com/releases/v5.0.6/css/all.css
844 ms864 ms9 KB34 KB200text/cssStylesheet
https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
844 ms862 ms1 KB1 KB200application/javascriptScript
https://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2
875 ms892 ms38 KB38 KB200application/font-woff2Font
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000 ms1 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
47 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
855 ms
8 ms
889 ms
8 ms
897 ms
21 ms
918 ms
8 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.

URL
Potential Savings
https://use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2
17 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
226 ms10 ms4 ms
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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Minimize Critical Requests Depth - 3 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 430 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

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

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 1 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.Optimize CSS Delivery of the following:

https://use.fontawesome.com/releases/v5.0.6/css/all.css

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://thekalam.in/
https://thekalam.in/
https://thekalam.in/cgi-sys/suspendedpage.cgi

Reduce server response time

In our test, your server responded in 0.26 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

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:

https://thekalam.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js (2 days)
Optimize images
Your images are optimized. Learn more about optimizing images.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does thekalam.in use compression?

thekalam.in use br compression.
Original size: 7.25 KB
Compressed size: 3.77 KB
File reduced by: 3.48 KB (47%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

thekalam.in supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: sni.cloudflaressl.com
Organization:
Location:
Issuer: CloudFlare Inc ECC CA-2
Valid from: Dec 6 00:00:00 2018 GMT
Valid until: Dec 6 12:00:00 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

thekalam.in supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 06 Sep 2019 08:06:04 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: max-age=3600
Expires: Fri, 06 Sep 2019 09:06:04 GMT
Location: https://thekalam.in/
Vary: Accept-Encoding
Server: cloudflare
CF-RAY: 511ef1032a30c63f-MSP

HTTP/2 302 
date: Fri, 06 Sep 2019 08:06:04 GMT
content-type: text/html; charset=iso-8859-1
set-cookie: __cfduid=d3bc429e1a5ab4c9f75473848cec7c8bc1567757164; expires=Sat, 05-Sep-20 08:06:04 GMT; path=/; domain=.thekalam.in; HttpOnly
location: https://thekalam.in/cgi-sys/suspendedpage.cgi
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 511ef1043f52c627-MSP

HTTP/2 200 
date: Fri, 06 Sep 2019 08:06:04 GMT
content-type: text/html
set-cookie: __cfduid=d3bc429e1a5ab4c9f75473848cec7c8bc1567757164; expires=Sat, 05-Sep-20 08:06:04 GMT; path=/; domain=.thekalam.in; HttpOnly
vary: Accept-Encoding
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 511ef105d889c627-MSP
content-encoding: br

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
NS leia.ns.cloudflare.com 3600
NS jeff.ns.cloudflare.com 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.inregistry.net...
\Error - could not open a connection to whois.inregistry.net
Last update was 168 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with thekalam.in in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

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) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
thekalam.in widget