Ishouldhave.sg
Visit ishouldhave.sgTigerair: i should have
Global rank | - |
---|---|
Daily visitors | - |
Daily pageviews | - |
Pageviews per user | 0 |
Rating | |
---|---|
Status | Offline |
Latest check |
Countable Data Brief
Ishouldhave.sg is tracked by us since August, 2015.
Ishouldhave has the lowest Google pagerank and bad results in terms of Yandex topical citation index. We found that Ishouldhave.sg is poorly ‘socialized’ in respect to any social network. According to Google safe browsing analytics, Ishouldhave.sg is quite a safe domain with no visitor reviews.
Worldwide Audience
Compare it to ...Ishouldhave.sg gets 84.2% of its traffic from Singapore where it is ranked #5355.
Top Countries
Singapore | 84.2% |
Top Ranks
Singapore | 5 355 |
Traffic Analysis
Compare it to ...It seems that the number of visitors and pageviews on this site is too low to be displayed, sorry.
Subdomains Traffic Shares
Ishouldhave.sg has no subdomains with considerable traffic.
SEO Stats
Compare it to ...Ishouldhave.sg is not yet effective in its SEO tactics: it has Google PR 0. It may also be penalized or lacking valuable inbound links.
Homepage Top Backlinks PR
No data
Top Keywords % of search traffic
tigerair | 84.10% |
tiger air | 14.48% |
Singapore Airlines | 0.73% |
tigerairways | 0.31% |
i should have | 0.22% |
Domain Registration Data
Compare it to ...General
8 years ago Expired on April 07, 2016 |
9 years old Created on April 07, 2015 |
9 years ago Changed at April 08, 2015 |
Registrar and Status
Registar | SAFENAMES LIMITED |
Status |
OK VerifiedID@SG-Mandatory VerifiedID@SG-OK |
In Other TLDs
No data
Server Information
Compare it to ...IP Whois
No data
Server Technologies
-
Apache HTTP Server
Backend server
DNS Records
Nameservers
- dns1.idp365.net
- dns2.idp365.net
- dns3.idp365.net
host | value | ttl |
---|---|---|
ishouldhave.sg | 119.9.43.22 |
899 |
host | value | ttl | pri |
---|---|---|---|
ishouldhave.sg | mx2.emailsrvr.com |
899 | 10 |
ishouldhave.sg | mx1.emailsrvr.com |
899 | 10 |
host | value | ttl |
---|---|---|
ishouldhave.sg | dns2.idp365.net |
8639 |
ishouldhave.sg | dns1.idp365.net |
8639 |
ishouldhave.sg | dns3.idp365.net |
8639 |
host | value | ttl |
---|---|---|
ishouldhave.sg | Mname: dns1.idp365.net |
8639 |
Safety
Compare it to ...Safety status of Ishouldhave.sg is described as follows: Google Safe Browsing reports its status as safe.
Get more Ishouldhave.sg reviews
MyWOT
Overall reputation | Unknown |
---|---|
Trustworthiness | Unknown |
Privacy | Unknown |
Child safety | Unknown |
Google Safe Browsing
Website status | Safe |
---|---|
Status | ok |
User reviews
Reputation | Unknown | |
---|---|---|
0 positive0 negative |
Social Engagement
Compare it to ...Ishouldhave.sg has 0% of its total traffic coming from social networks (in last 3 months) and the most active engagement is detected in Facebook (854 shares)
Social Metrics Get more Ishouldhave.sg social history
0%
of total traffic in last 3 months is social0
Facebook likes854
Facebook shares0
Twitter mentions0
Google pluses0
LinkedIn mentions0
Pinterest pins0
StumbleUpon views