Statistics

WORKING MOMS RESOURCE | Support for Moms Who Work

www.workingmomsresource.com/

It's been the subject of some controversial news stories and books lately, but I still don't think it gets enough attention. And so I've decided to DO something

Workingmomsresource.com

Conversion Technology Metas Server

Workingmomsresource.com is hosted in United States / Provo . Workingmomsresource.com uses HTTPS protocol. Number of used technologies: 8. First technologies: CSS, Font Awesome, Html, Number of used javascripts: 5. First javascripts: Jquery.js, Jquery-migrate.min.js, Bootstrap.js, Number of used analytics tools: 1. First analytics tools: Google Analytics, Number of used plugins, modules: 1. Its server type is: nginx/1.10.1. Its CMS is: Wordpress.

Technologies in use by Workingmomsresource.com

Technology

Number of occurences: 8

CSS
Font Awesome
Html
Html5
Javascript
jQuery
Php
Pingback

Javascripts

Number of occurences: 5

jquery.js
jquery-migrate.min.js
bootstrap.js
script.js
wp-embed.min.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

Google Analytics

Server Type

nginx/1.10.1

Used plugins, modules

Number of plugins and modules: 1

add to any

Conversion rate optimization
Clickable call number	Not founded!
Conversion form (contact form, subcriber)	Not founded!
Clickable email	Not founded!
CTA (call to action) button	Founded!
List	Founded!
Image	Not founded!
Enhancement	Not founded!
Responsive website	Founded!
Facebook sharing	Not founded!
Google+ sharing	Not founded!
Twitter sharing	Not founded!
Linkedin sharing	Not founded!
Blog on the webiste	Not founded!

HTTPS (SSL) - Workingmomsresource.com

SSL certificate

name: /OU=Domain Control Validated/OU=Hosted by BlueHost.Com, INC/OU=PositiveSSL Wildcard/CN=*.bluehost.com
subject:
- OU:
  - 0: Domain Control Validated
  - 1: Hosted by BlueHost.Com, INC
  - 2: PositiveSSL Wildcard
- CN: *.bluehost.com
hash: b00471fb
issuer:
- C: GB
- ST: Greater Manchester
- L: Salford
- O: COMODO CA Limited
- CN: COMODO RSA Domain Validation Secure Server CA
version: 2
serialNumber: 275919344465328667035358918366332841359
validFrom: 150313000000Z
validTo: 180312235959Z
validFrom_time_t: 1426204800
validTo_time_t: 1520899199
extensions:
- authorityKeyIdentifier: keyid:90:AF:6A:3A:94:5A:0B:D8:90:EA:12:56:73:DF:43:B4:3A:28:DA:E7
- subjectKeyIdentifier: 29:B6:2F:A5:A8:41:C7:45:BE:86:84:10:E9:26:A7:94:67:64:BC:73
- keyUsage: Digital Signature, Key Encipherment
- basicConstraints: CA:FALSE
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- certificatePolicies: Policy: 1.3.6.1.4.1.6449.1.2.2.7 CPS: https://secure.comodo.com/CPS Policy: 2.23.140.1.2.1
- crlDistributionPoints: Full Name: URI:http://crl.comodoca.com/COMODORSADomainValidationSecureServerCA.crl
- authorityInfoAccess: CA Issuers - URI:http://crt.comodoca.com/COMODORSADomainValidationSecureServerCA.crt OCSP - URI:http://ocsp.comodoca.com
- subjectAltName: DNS:*.bluehost.com, DNS:bluehost.com

Meta - Workingmomsresource.com

Number of occurences: 5

Name:
Content:
Name: viewport
Content: width=device-width, initial-scale=1
Name: description
Content: It's been the subject of some controversial news stories and books lately, but I still don't think it gets enough attention. And so I've decided to DO something
Name: generator
Content: WordPress 4.5.3
Name: msapplication-TileImage
Content: http://workingmomsresource.com/wp-content/uploads/2016/06/12994317_601919433309385_310989625176260062_n.jpg

Server / Hosting

IP: 50.87.248.181
Latitude: 40.22
Longitude: -111.61
Country: United States
City: Provo

Rname

ns2.bluehost.com
ns1.bluehost.com
mail.workingmomsresource.com

Target

root.box1181.bluehost.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx/1.10.1 Date: Thu, 04 Aug 2016 15:19:55 GMT Content-Type: text/html; charset=UTF-8 Content-Length: 0 Location: http://workingmomsresource.com/ Vary: Accept-Encoding X-Cache: MISS from s_mf18 X-Cache-Lookup: MISS from s_mf18:80 Via: 1.1 s_mf18 (squid/3.5.9) Connection: keep-alive HTTP/1.1 200 OK Server: nginx/1.10.1 Date: Thu, 04 Aug 2016 15:19:56 GMT Content-Type: text/html; charset=UTF-8 Link: ; rel="https://api.w.org/" Vary: Accept-Encoding X-Cache: MISS from s_mf18 X-Cache-Lookup: MISS from s_mf18:80 Transfer-Encoding: chunked Via: 1.1 s_mf18 (squid/3.5.9) Connection: keep-alive