geero.net Report : Visit Site

Technical data of the geero.net

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host geero.net. Currently, hosted in United Kingdom and its service provider is 34SP.com Limited .

the related websites

galeon.com walmart.com hse.gov.uk maplin.co.uk theborneopost.com netnames.com 888.com dailyrecord.co.uk avanquest.com nhm.ac.uk 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.2.15 (CentOS) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

geero.net search primary menu skip to content about me email me prayermate bible games directx exporter privacy policy search for: prayermate , uncategorized advent 2017 on prayermate november 24, 2017 andy geers i’m delighted to announce this year’s range of advent devotionals available through prayermate – get the lowdown on the prayermate blog . coding for christ kingdom code build ’17 – christian hackathon weekend september 25, 2017 andy geers for the third year running, kingdom code uk will be hosting a hackathon weekend for christians in the world of technology – an opportunity for christian coders, designers, project managers, tech entrepreneurs and general enthusiasts to gather for 48 hours to build new technologies inspired by our christian faith. this year we’re hugely privileged to be partnering with two excellent christian charities: christians against poverty and home for good . they’ve each set a challenge (below) and hopefully it will be a fantastic weekend! not convinced it’s for you? read my post from last year: why you should attend the hackathon (and some bad reasons not to). with a month still to go we’ve already got 50 signed up but we’re praying for 100. book your ticket today ! coding for christ , prayermate how to encrypt a google firebase realtime database may 24, 2017 andy geers the problem: protecting sensitive user data in firebase realtime database for a while now i’ve been working on implementing user accounts in the prayermate app so that users can sync their private data to the cloud and share it between their different devices. think of prayermate as being like an evernote equivalent but specifically focussed on recording different prayer needs – some of them ones of a highly personal nature either about yourself or about close friends that you’re praying for. ever since google announced their revamped version of firebase a year ago i’ve been in love with it as a platform – the firebase realtime database in particular makes authenticating users and syncing their data to the cloud as easy as pie. but there’s one big drawback: anybody with admin credentials for the firebase project can browse all of that private user data at will. equally, google’s infrastructure is pretty rock solid in terms of security (i went to a presentation about it at the recent google cloud next conference in london – and it is seriously cool stuff) but the consequences of a hacker getting hold of all of that user data doesn’t even bear thinking about. that’s why i’ve been looking for a solution that allows users to still sync all of their data between their devices via firebase, but whilst preventing me as the developer (or anybody else who somehow got hold of a data dump) from reading that data. at the same time, i wanted to do it in a way that meant a user who lost their phone wasn’t completely locked out of all of their data for all time – even people with just a single device are frequently asking me to implement sync as a backup mechanism. thankfully google’s own infrastructure provides some really cool tools that made solving this surprisingly easy – and since even people within google / firebase themselves didn’t seem overly aware of what was on offer, i thought it was worth blogging about my experiences. step 1: a cross-platform encryption/decryption solution – rncryptor my first day of this project was spent looking for an encryption/decryption library that met the following requirements: data could be decrypted across both ios and android phones production ready / stable actively maintained actually secure performant (fast encryption / decryption) considering the year is 2017 this was a remarkably difficult exercise. almost every library i came across had huge warnings either on the ios version or the android version saying “the library on the other platform uses really insecure defaults which i had to incorporate for compatibility purposes”, or it hadn’t been touched in four years, or it had a gazillion issues logged against it. i eventually settled on rncryptor-objc / rncryptornative . when i last looked at rncryptor a few years back the only option on android was jncryptor which was ridiculously slow (multiple seconds per operation) and which i now notice is covered in warnings saying “do not use on android”. step 2: securely synced encryption keys using google cloud kms with rncryptor implemented on both platforms, that just left the little issue of how to actually sync the user’s encryption key between their devices. a naive solution would be to store that key within the firebase database itself – that would at least prevent me from accidentally reading people’s private data (at least nothing would be stored in plain text) but would still make it trivial for anybody with access to the firebase data to decrypt anything they wanted to. at google cloud next i came across the google cloud key management service , and could immediately tell there was some potential here. the google cloud kms lets you create encryption keys which can then be used to encrypt and decrypt data. my first assumption was that i’d generate a key for every user, but for prayermate’s 25,000 monthly active users that would quickly reach at least $1,500 every single month. after a chat with some of the very helpful google developer advocates i quickly realised that wasn’t what i needed at all – just a single kms key could be used to encrypt and decrypt a user’s data encryption key (dek). in the end what i came up with was to build a super-simple authentication service in the google app engine flexible environment. when a user first logs in to prayermate, the auth service generates them a new dek which it gives to them, as well as encrypting it in kms for storage in firebase. when the user logs in to their second device, the auth service takes the encrypted key from firebase and again uses kms to decrypt it for the user to store in their device’s local keychain (where it is again stored in encrypted form). importantly, the kms key belongs to a different google account to the firebase database, so no one user (e.g. me) has permission to both read the data and decrypt it. a hacker would need to compromise both accounts to access the unencrypted data. step 3: authentication of firebase users via google cloud endpoints where things get really cool, however, is with the introduction of google cloud endpoints in to the mix. this is basically a proxy layer that sits between your user and your backend, but which, crucially, understands the concept of firebase authenticated users and can validate those logins and tell your backend who somebody is. this means that each time we generate a new dek for a user we can encrypt it along with their user id, so that when somebody comes along later requesting to decrypt a particular dek the backend can verify if it actually belongs to them. on the whole, the documentation for google cloud endpoints is pretty good, and if you persevere long enough you can probably figure out how to get it working. i got stuck on a couple of points: firstly, i got myself in a muddle about what to put in the endpoints_api_service section of app.yaml and how it related to the host property of openapi.yaml . there are so many different deployment combinations that the endpoints documentation struggles to make it very clear – but if you are deploying to the flexible app engine you just use the same [project_id].appspot.com form in both places, and your endpoints_api_service.config_id is just what you get given when you deploy your proxy configuration using gcloud service-management deploy openapi.yaml (usually something like “2017-01-01r0″). the second place where i got really stuck for a while is how to actually enable firebase authentication on the backend. the endpoints documentation talked about a x-endpoint-api-userinfo header but for the life of me i could not get it to be injected at all. eventually, i discovered the missing instruction from the d

URL analysis for geero.net

http://www.geero.net/category/featured-posts/
http://www.geero.net/2015/12/
http://www.geero.net/2010/02/
http://www.geero.net/2015/08/
http://www.geero.net/2014/04/
http://www.geero.net/2015/10/code-for-the-kingdom-global-hackathon/
http://www.geero.net/wp-content/uploads/18_prayers_unbelievers.jpg
http://www.geero.net/2012/11/
http://www.geero.net/wp-content/uploads/precdac15_3.jpg
http://www.geero.net/category/hubbub/
http://www.geero.net/2013/06/
http://www.geero.net/2015/08/developers-and-designers-serving-god-with-their-gifts/
http://www.geero.net/2011/04/
http://www.geero.net/2012/12/
http://www.geero.net/category/just-thinking/
beta.hubbub.co.uk
kingdomcode.uk
hubbub.co.uk
developers.hubbub.co.uk
stakeholders.ofcom.org.uk
zazzle.co.uk
premierdigital.org.uk
thegoodbook.co.uk
homeforgood.org.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: GEERO.NET
Domain ID: 95982204_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.easyspace.com
Registrar URL: www.easyspace.com
Updated Date: 2016-03-21T12:15:27Z
Creation Date: 2003-03-20T15:13:40Z
Registrar Registration Expiration Date: 2018-03-20T14:13:40Z
Registrar: Easyspace Ltd.
Registrar IANA ID: 79
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +44.3707555066
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: Andrew Geers
Registrant Organization: Andrew Geers
Registrant Street: 12 Burgess Park Mansions
Registrant City: Fortune Green Road
Registrant State/Province: London
Registrant Postal Code: NW6 1DP
Registrant Country: GB
Registrant Phone: +44.7814991376
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID:
Admin Name: Andrew Geers
Admin Organization: Andrew Geers
Admin Street: 12 Burgess Park Mansions
Admin City: Fortune Green Road
Admin State/Province: London
Admin Postal Code: NW6 1DP
Admin Country: GB
Admin Phone: +44.7814991376
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID:
Tech Name: 34SP 34SP Host master
Tech Organization: 34SP.com
Tech Street: 37 Turner Street
Tech City: Manchester
Tech State/Province: Greater Manchester
Tech Postal Code: M4 1DW
Tech Country: GB
Tech Phone: +44.1612340897
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: [email protected]
Name Server: NS.34SP.COM
Name Server: NS2.34SP.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2016-03-21T12:15:27Z <<<

"For more information on Whois status codes, please visit https://icann.org/epp"

The Data in the EASYSPACE Registrar WHOIS database is provided to you by
EASYSPACE for information purposes only, and may be used to assist you in
obtaining information about or related to a domain name's registration record.

EASYSPACE makes this information available "as is," and does not guarantee its accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of EASYSPACE.

EASYSPACE reserves the right to terminate your access to the EASYSPACE
WHOIS database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this policy.

EASYSPACE reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

  REGISTRAR EASYSPACE LTD.

  REFERRER http://www.easyspace.com

SERVERS

  SERVER net.whois-servers.net

  ARGS domain =geero.net

  PORT 43

  SERVER whois.easyspace.com

  ARGS geero.net

  PORT 43

  TYPE domain

DOMAIN

  NAME geero.net

NSERVER

  NS.34SP.COM 80.82.112.108

  NS2.34SP.COM 89.21.0.52

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

  CHANGED 2016-03-21

  CREATED 2003-03-20

  EXPIRES 2018-03-20

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .