Ike Lins Personal Blog

tail -f web.log

OVERVIEW

The web site ikelin.com currently has an average traffic classification of zero (the smaller the more users). There is one contacts and locations for ikelin.com to help you communicate with them. The web site ikelin.com has been on the internet for six hundred and ninety-two weeks, eight days, nine hours, and thirty-three minutes.
Contacts
1
Addresses
1
Online Since
Jun 2011

IKELIN.COM TRAFFIC

The web site ikelin.com has seen variant quantities of traffic throughout the the year.
Traffic for ikelin.com

Date Range

1 week
1 month
3 months
This Year
Last Year
All time
Traffic ranking (by month) for ikelin.com

Date Range

All time
This Year
Last Year
Traffic ranking by day of the week for ikelin.com

Date Range

All time
This Year
Last Year
Last Month

IKELIN.COM HISTORY

The web site ikelin.com was created on June 23, 2011. This website was updated on the date of May 25, 2013. It will expire on June 23, 2015. It is currently six hundred and ninety-two weeks, eight days, nine hours, and thirty-three minutes old.
REGISTERED
June
2011
UPDATED
May
2013
EXPIRED
June
2015

SPAN

13
YEARS
3
MONTHS
7
DAYS

LINKS TO WEBSITE

WHAT DOES IKELIN.COM LOOK LIKE?

Desktop Screenshot of ikelin.com Mobile Screenshot of ikelin.com Tablet Screenshot of ikelin.com

CONTACTS

A HAPPY DREAMHOST CUSTOMER

PRIVATE REGISTRANT

417 ASSOCIATED RD #324 C/O IKELIN.COM

BREA, CA, 92821

US

IKELIN.COM SERVER

Our crawlers detected that a lone root page on ikelin.com took three hundred and sixty-six milliseconds to download. We could not detect a SSL certificate, so in conclusion our crawlers consider ikelin.com not secure.
Load time
0.366 sec
SSL
NOT SECURE
IP
173.236.153.221

NAME SERVERS

ns1.dreamhost.com
ns2.dreamhost.com
ns3.dreamhost.com

WEBSITE ICON

SERVER SOFTWARE AND ENCODING

We revealed that this website is employing the Apache operating system.

HTML TITLE

Ike Lins Personal Blog

DESCRIPTION

tail -f web.log

PARSED CONTENT

The web site ikelin.com has the following in the homepage, "Implementing ETag Caching with Jersey." I noticed that the website also stated " When utilizing ETag for RESTful service caching, we typically expect the following behavior." They also said " First, the network bandwidth is reduced with 304 because entities are not sent back to the client. Second, the server load is reduced because 304 and 412 will prevent the server from further processing the request. Continue reading Implementing ETag Caching with Jersey ."

ANALYZE SIMILAR WEBSITES

IkeLinkGREEN Boyd DeviantArt

This is the place where you can personalize your profile! By moving, adding and personalizing widgets. You can drag and drop to rearrange. You can edit widgets to customize them. The bottom has widgets you can add! Some widgets you can only access when you get Core Membership.