Bellinghambiblechapel.org

Bellinghambiblechapel.org is hosted in United States / San Francisco . Bellinghambiblechapel.org uses HTTPS protocol. Number of used technologies: 8. First technologies: CSS, Gravatar, Html, Number of used javascripts: 5. First javascripts: Gprofiles.js, Wpgroho.js, Widgets.js, Number of used analytics tools: 1. First analytics tools: ComScore, Its server type is: nginx. Its CMS is: Wordpress.

Technologies in use by Bellinghambiblechapel.org

Technology

Number of occurences: 8

CSS
Gravatar
Html
Html5
Javascript
Php
Pingback
Shortcodes

Javascripts

Number of occurences: 5

gprofiles.js
wpgroho.js
widgets.js
725X1342.skimlinks.js
w.js

Content Management System

Number of occurences: 1

Wordpress

Analytics

Number of occurences: 1

comScore

Advertise

Number of occurences: 1

Skimlinks

Server Type

nginx

Social

Number of occurences: 1

Twitter Button

Conversion rate optimization
Clickable call number	Not founded!
Conversion form (contact form, subcriber)	Founded!
Clickable email	Founded!
CTA (call to action) button	Founded!
List	Founded!
Image	Not founded!
Enhancement	Not founded!
Responsive website	Not 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) - Bellinghambiblechapel.org

SSL certificate

name: /CN=tls.automattic.com
subject:
- CN: tls.automattic.com
hash: 6338c477
issuer:
- C: US
- O: Let's Encrypt
- CN: Let's Encrypt Authority X3
version: 2
serialNumber: 285815701004929418989414223452471179017502
validFrom: 160404110600Z
validTo: 160703110600Z
validFrom_time_t: 1459767960
validTo_time_t: 1467543960
extensions:
- keyUsage: Digital Signature, Key Encipherment
- extendedKeyUsage: TLS Web Server Authentication, TLS Web Client Authentication
- basicConstraints: CA:FALSE
- subjectKeyIdentifier: 52:3C:7C:D7:C1:07:86:E2:9F:FD:FF:4E:6A:B0:A2:1F:29:AD:85:A8
- authorityKeyIdentifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
- authorityInfoAccess: OCSP - URI:http://ocsp.int-x3.letsencrypt.org/ CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
- subjectAltName: DNS:bellezacaninabc.com, DNS:bellezaconsalud.com, DNS:bellezadechat.com, DNS:bellezagris.com, DNS:bellezaperegrina.com, DNS:bellezasantarua.es, DNS:bellezasingular.com, DNS:bellezatotaltv.com, DNS:bellezatropicalblog.com, DNS:bellezavn.com, DNS:bellezaysaludconaloe.com, DNS:bellezaysaludcorporal.co, DNS:bellezza4you.it, DNS:bellezzabychristy.com, DNS:bellezzabylinda.com, DNS:bellezzainthecity.com, DNS:bellezzamondana.com, DNS:bellezzanellavita.com, DNS:bellezzaskincareclinic.com, DNS:bellfamilyfarmproductions.com, DNS:bellfamilyreunion2014.com, DNS:bellflowersblog.com, DNS:bellgab.co, DNS:bellgameparty.com, DNS:bellgraphicdesign.org, DNS:bellhousebnb.com, DNS:bellhousetutoring.com, DNS:belliahpfabdesigns.com, DNS:bellicimohangers.com, DNS:bellideroma.com, DNS:belliesandbabiesnc.com, DNS:bellifly.com, DNS:belligerentantigrammarian.com, DNS:belligerentman.com, DNS:bellingenpasta.com, DNS:bellingfam.com, DNS:bellinghambiblechapel.org, DNS:bellinghamhealingcenter.com, DNS:bellinghamiww.com, DNS:bellinghammn.com, DNS:bellinifolkschool.com, DNS:bellinisandblush.com, DNS:bellinistoblooms.com, DNS:bellinzacademy.com, DNS:bellissimaglass.com, DNS:bellissimaroma.com, DNS:bellissimaspazi.com, DNS:bellitannerbikes.com, DNS:belllez.com, DNS:blog.bellflowers.com, DNS:tls.automattic.com
- certificatePolicies: Policy: 2.23.140.1.2.1 Policy: 1.3.6.1.4.1.44947.1.1.1 CPS: http://cps.letsencrypt.org User Notice: Explicit Text: This Certificate may only be relied upon by Relying Parties and only in accordance with the Certificate Policy found at https://letsencrypt.org/repository/

Meta - Bellinghambiblechapel.org

Number of occurences: 10

Name:
Content: en_US
Name: generator
Content: WordPress.com
Name: twitter:site
Content: @wordpressdotcom
Name: theme-color
Content: #9a92a0
Name: application-name
Content: Bellingham Bible Chapel
Name: msapplication-window
Content: width=device-width;height=device-height
Name: msapplication-tooltip
Content: Where two or three are gathered...
Name: msapplication-task
Content: name=WordPress.com Forums;action-uri=http://forums.wordpress.com/;icon-uri=https://s2.wp.com/i/favicon.ico
Name: title
Content: Bellingham Bible Chapel on WordPress.com
Name: description
Content: Where two or three are gathered...

Server / Hosting

IP: 192.0.78.24
Latitude: 37.75
Longitude: -122.42
Country: United States
City: San Francisco

Rname

ns1.wordpress.com
ns2.wordpress.com
ns3.wordpress.com

Target

hostmaster.wordpress.com

HTTP Header Response

HTTP/1.1 301 Moved Permanently Server: nginx Date: Mon, 09 May 2016 00:51:41 GMT Content-Type: text/html Content-Length: 178 Location: https://bellinghambiblechapel.org/ X-ac: 3.fra _dfw X-Cache: MISS from s_xt40 X-Cache-Lookup: MISS from s_xt40:80 Via: 1.1 s_xt40 (squid/3.5.14) Connection: keep-alive HTTP/1.1 200 Connection established HTTP/1.1 200 OK Server: nginx Date: Mon, 09 May 2016 00:51:42 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive Strict-Transport-Security: max-age=86400 Vary: Accept-Encoding Vary: Cookie X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header. Link: ; rel=shortlink X-ac: 3.fra _dfw