Web Analysis for Howthingshouldbe - howthingshouldbe.com
2.85
Rating by CuteStat
howthingshouldbe.com is 6 years 3 weeks old. It is a domain having com extension. This website is estimated worth of $ 8.95 and have a daily income of around $ 0.15. As no active threats were reported recently by users, howthingshouldbe.com is SAFE to browse.
PageSpeed Score
71
Siteadvisor Rating
Not Applicable
Traffic Report
Daily Unique Visitors: | Not Applicable |
Daily Pageviews: | Not Applicable |
Estimated Valuation
Income Per Day: | $ 0.15 |
Estimated Worth: | $ 8.95 |
Search Engine Indexes
Google Indexed Pages: | Not Applicable |
Bing Indexed Pages: | Not Applicable |
Search Engine Backlinks
Google Backlinks: | Not Applicable |
Bing Backlinks: | Not Applicable |
Safety Information
Google Safe Browsing: | No Risk Issues |
Siteadvisor Rating: | Not Applicable |
WOT Trustworthiness: | Not Applicable |
WOT Child Safety: | Not Applicable |
Website Ranks & Scores
Alexa Rank: | Not Applicable |
Domain Authority: | Not Applicable |
Web Server Information
Page Resources Breakdown
Homepage Links Analysis
Website Inpage Analysis
H1 Headings: | 1 | H2 Headings: | 11 |
H3 Headings: | 2 | H4 Headings: | Not Applicable |
H5 Headings: | Not Applicable | H6 Headings: | Not Applicable |
Total IFRAMEs: | Not Applicable | Total Images: | 14 |
Google Adsense: | Not Applicable | Google Analytics: | Not Applicable |
Websites Hosted on Same IP (i.e. 165.227.8.144)
HTTP Header Analysis
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Fri, 06 Apr 2018 19:37:53 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Link: <https://howthingshouldbe.com/wp-json/>; rel="https://api.w.org/"
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
Server: nginx/1.10.3 (Ubuntu)
Date: Fri, 06 Apr 2018 19:37:53 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Link: <https://howthingshouldbe.com/wp-json/>; rel="https://api.w.org/"
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
Domain Information
Domain Nameserver Information
DNS Record Analysis
Host | Type | TTL | Extra |
---|---|---|---|
howthingshouldbe.com | A | 300 |
IP: 165.227.8.144 |
howthingshouldbe.com | NS | 300 |
Target: ns1mtw.name.com |
howthingshouldbe.com | NS | 300 |
Target: ns4dls.name.com |
howthingshouldbe.com | NS | 300 |
Target: ns2fjz.name.com |
howthingshouldbe.com | NS | 300 |
Target: ns3fhx.name.com |
howthingshouldbe.com | SOA | 300 |
MNAME: ns1mtw.name.com RNAME: support.name.com Serial: 1522912903 Refresh: 10800 Retry: 3600 Expire: 604800 Minimum TTL: 3600 |
Full WHOIS Lookup
Domain Name: HOWTHINGSHOULDBE.COM
Registry Domain ID: 2248103752_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2018-04-05T07:10:03Z
Creation Date: 2018-04-05T07:10:02Z
Registry Expiry Date: 2019-04-05T07:10:02Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: 7202492374
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1MTW.NAME.COM
Name Server: NS2FJZ.NAME.COM
Name Server: NS3FHX.NAME.COM
Name Server: NS4DLS.NAME.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-04-06T19:37:39Z
Registry Domain ID: 2248103752_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2018-04-05T07:10:03Z
Creation Date: 2018-04-05T07:10:02Z
Registry Expiry Date: 2019-04-05T07:10:02Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: 7202492374
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1MTW.NAME.COM
Name Server: NS2FJZ.NAME.COM
Name Server: NS3FHX.NAME.COM
Name Server: NS4DLS.NAME.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-04-06T19:37:39Z