pu-gh.com Report : Visit Site


  • Ranking Alexa Global: # 5,678,356

    Server:GitHub.com...

    The main IP address: 185.11.240.169,Your server United Kingdom,Chilwell ISP:Daily Internet Services  TLD:com CountryCode:GB

    The description :twitter github tech stuff tales from the trenches jquery/underscore/lodash extend, without the mutation 23 feb 2015 i was writing a little javascript today where i wanted to scale a bunch of coordinat...

    This report updates in 20-Jun-2018

Created Date:2007-01-07
Changed Date:2017-03-02
Expires Date:2018-01-07

Technical data of the pu-gh.com


Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host pu-gh.com. Currently, hosted in United Kingdom and its service provider is Daily Internet Services .

Latitude: 52.911800384521
Longitude: -1.236310005188
Country: United Kingdom (GB)
City: Chilwell
Region: England
ISP: Daily Internet Services

the related websites

HTTP Header Analysis


HTTP Header information is a part of HTTP protocol that a user's browser sends to called GitHub.com containing the details of what the browser wants and will accept back from the web server.

X-Timer:S1529461968.236252,VS0,VE13
Content-Length:8362
Via:1.1 varnish
X-Cache:MISS
Content-Encoding:gzip
X-GitHub-Request-Id:42DC:3BF1:2E5D256:4048669:5B29BCCF
Accept-Ranges:bytes
Expires:Wed, 20 Jun 2018 02:42:48 GMT
Vary:Accept-Encoding
Server:GitHub.com
Last-Modified:Mon, 23 Feb 2015 14:27:55 GMT
Connection:keep-alive
X-Served-By:cache-jfk8128-JFK
X-Cache-Hits:0
Cache-Control:max-age=600
Date:Wed, 20 Jun 2018 02:32:48 GMT
Access-Control-Allow-Origin:*
X-Fastly-Request-ID:ab7bbf3374637c1149533ae9526d29c2824b799f
Content-Type:text/html; charset=utf-8
Age:0

DNS

soa:ns1.3v0.net. problems.evohosting.co.uk. 2015093001 86400 7200 3600000 86400
ns:ns1.3v0.net.
ns3.3v0.net.
ns4.3v0.net.
ns2.3v0.net.
ipv4:IP:185.11.240.169
ASN:198047
OWNER:UKWEB-EQX, GB
Country:GB
mx:MX preference = 0, mail exchanger = pu-gh.com.

HtmlToText

twitter github tech stuff tales from the trenches jquery/underscore/lodash extend, without the mutation 23 feb 2015 i was writing a little javascript today where i wanted to scale a bunch of coordinate data from a source object to a new set of scaled objects. so i did something like this... var originaldata = json . parse ( source ); var scaleddata = _ . extend ( originaldata , { objects : _ . map ( toscaledobject , originaldata . objects )} ); but surprisingly didn't get the results i expected. turns out firstly i had the arguments to map the wrong way around, but before realising this i also noticed that my original source object was also getting updated. wat?!? destination object after checking the docs i realised both jquery and underscore/lodash refer to the first object passed to the extend function as the destination object. so while the function also (curiously) returns this destination object, it is in fact mutated in-place as part of the extend operation. the workaround the workaround i used was to provide a new object for this destination object, and then as part of extend map the source object onto this. like... var originaldata = json . parse ( source ); var scaleddata = _extend ( {}, originaldata , { objects : _ . map ( originaldata . objects , toscaledobject )} ); simple enough. so library writers please try to be immutable by default. jquery ui onchangemonthyear event gotchas 26 jan 2015 today involved fixing a bug where i have a some date fields that use the datepicker component from jquery ui, and i've added some helper links next to them when you can set the date to 3, 6 12, etc months in the future. the bug reported was that these links only work the second time they are clicked. hmmm... i spent more time than i'd like to admit reading and stepping through the code to work out what was going on, and just found myself going round in circles. onchangemonthyear recently i had added a hook for the event onchangemonthyear so that when the user changed the month or year from the open datepicker it would default to the first of that month (as this is what my users usually want to do, and the out-of-the-box behaviour is to do nothing). here it is... var onchangemonthyearhandler = function ( year , month , inst ) { var picker = $ ( this ); var current = picker . datepicker ( 'getdate' ); if ( current ) { current . setdate ( 1 ); current . setyear ( year ); current . setmonth ( month - 1 ); picker . datepicker ( 'setdate' , current ); } }; gotcha #1 can you see my first bug? well, when setting the value of the datepicker via my helper links if the date being set is different to the current month/year of the datepicker then this event gets fired. the flow being... set date to 6 months in future onchangemonthyear fires onchangemonthyear handler sets the date to the first of the month doh! ok, so i guess it's expected and probably useful that this event fires both when the user changes the month/year via the control and also when the date is changed via the api. so here's my first fix, checking if the datepicker is visible... var onchangemonthyearhandler = function ( year , month , inst ) { var picker = $ ( this ); var current = picker . datepicker ( 'getdate' ); var isvisible = $ ( inst . dpdiv ). is ( ':visible' ); if ( isvisible && current ) { current . setdate ( 1 ); current . setyear ( year ); current . setmonth ( month - 1 ); picker . datepicker ( 'setdate' , current ); } }; gotcha #2 i thought this would have fixed it, but no... i can see that my check as to wether or not the datepicker is visible is working, and am confident it's required... but the date is still being set incorrectly and needs two clicks. after more debugging and code reading it turns out the bug comes from my usage of the getdate api method. this method does not just return the date from the datepicker, but in doing so mutates the internal state of the control. the flow being... set date to 6 months in future onchangemonthyear fires getdate called, which resets the date using current data (not applied from new date yet) doh! unfortunately there is no mention in the docs that calling any datepicker methods from within this handler could lead to undesirable results... gah! here's my fix... var onchangemonthyearhandler = function ( year , month , inst ) { var isvisible = $ ( inst . dpdiv ). is ( ':visible' ); if ( isvisible ) { var picker = $ ( this ); var current = picker . datepicker ( 'getdate' ); if ( current ) { current . setdate ( 1 ); current . setyear ( year ); current . setmonth ( month - 1 ); picker . datepicker ( 'setdate' , current ); } } }; i'm only trying to set the date to the 1st if the datepicker is open, but also only accessing the current date of the control when this is the case. this means that when the handler fires after the date has been set programatically it won't step in and bugger things up. conclusion my take away from this is a reminder as to the complications and dangers of managing state, and how immutability makes things safer and less unexpected. i took a look to see if i could contribute this note to the official docs but there was no obvious way to do so. p.s. i'm aware of javascript scope rules and the fact my picker and current vars are actually visible to the entire function, but i prefer to ignore particular gotcha in favour of readability. update after writing this i realised that my second gotcha (while valid) is actually calling the getdate api unnecessarily. so i've cleaned it up a little... var onchangemonthyearhandler = function ( year , month , inst ) { var isvisible = $ ( inst . dpdiv ). is ( ':visible' ); if ( isvisible ) { var current = new date (); current . setdate ( 1 ); current . setyear ( year ); current . setmonth ( month - 1 ); $ ( this ). datepicker ( 'setdate' , current ); } }; which then avoids the second gotcha entirely! mysql datetime indexes and intervals 14 jan 2015 today i ran into an interesting (though afterwards 'doh! of course...') problem involving a slow mysql query that should have been a hell of a lot quicker. the application i work on supports users in many timezones, so when it comes to query time we always need to adjust system recorded times (which are always utc) to allow for the users current timezone. so for example consider a table... 1 create table mytable ( 2 id int unsigned not null auto_increment , 3 date_created datetime not null , 4 key date_created_idx ( date_created ), 5 primary key ( id ) 6 ); and a made-up query against it, where :tzoffset is the users utc offset in hours, and :thedate is a datetime we'd like to query against... 1 select * 2 from mytable 3 where date_created + interval : tzoffset hour > : thedate given a relatively small number of rows you'll have no problem with this, but open the explain output and you'll notice mysql ignores the index. change perspective i suppose it makes sense that mysql is now unable to use the index, it's an index on the date_created column, not on the date_created_plus_some_timezone_ column. so the fix is to move the date wrangling to the query parameter instead. 1 select * 2 from mytable 3 where date_created > : thedate - interval : tzoffset hour notice how the sign on the interval modifier changes as we're moving the date the other way. you could of course do this calculation on the date before binding it to the query, but in my case we often need to do the interval adjustment on the column itself so it's nicer to keep it in one place. a reminder to always keep one eye on explain ... drawing rings with css 30 sep 2014 i mentioned in my last post that the main application i work on has just undergone a redesign. one part of this was adding more visual goodness to the dashboard which greets users on login and serves as their information overview hub. a new component here displayed a progress wheel to keep the user up to date with their target for the month. here's the finished article... so how to render this... let's prete

URL analysis for pu-gh.com


http://blog.pu-gh.com///2014/09/28/server-to-client-templating/
http://blog.pu-gh.com///2015/01/14/mysql-datetime-indexes-and-intervals/
http://blog.pu-gh.com///2015/02/23/jquery-underscore-lodash-non-mutating-extend/
http://blog.pu-gh.com///2015/01/26/jquery-ui-on-year-month-change-gotcha/
http://blog.pu-gh.com///page2
http://blog.pu-gh.com///2014/09/30/drawing-rings-with-css/

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: PU-GH.COM
Registry Domain ID: 743873227_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: www.enom.com
Updated Date: 2017-03-02T09:39:20.00Z
Creation Date: 2007-01-07T16:23:10.00Z
Registrar Registration Expiration Date: 2018-01-07T16:23:10.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: RHODRI PUGH
Registrant Organization:
Registrant Street: 11, MILLFIELD
Registrant City: BRIDGEND
Registrant State/Province: BRIDGEND
Registrant Postal Code: CF31 4JG
Registrant Country: GB
Registrant Phone: +44.4401656468362
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID:
Admin Name: EVOHOSTING SUPPORT TEAM
Admin Organization: EVOHOSTING.CO.UK
Admin Street: 40 LABURNHAM ROAD
Admin Street: NIRVANA- SHERWOOD LANE
Admin City: MAIDENHEAD
Admin State/Province:
Admin Postal Code: SL6 4DE
Admin Country: GB
Admin Phone: +1.1628878101
Admin Phone Ext:
Admin Fax: +1.1628878121
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID:
Tech Name: EVOHOSTING SUPPORT TEAM
Tech Organization: EVOHOSTING.CO.UK
Tech Street: 40 LABURNHAM ROAD
Tech Street: NIRVANA- SHERWOOD LANE
Tech City: MAIDENHEAD
Tech State/Province:
Tech Postal Code: SL6 4DE
Tech Country: GB
Tech Phone: +1.1628878101
Tech Phone Ext:
Tech Fax: +1.1628878121
Tech Fax Ext:
Tech Email: [email protected]
Name Server: NS1.3V0.NET
Name Server: NS2.3V0.NET
Name Server: NS3.3V0.NET
Name Server: NS4.3V0.NET
DNSSEC: unSigned
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4252982646
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2017-03-02T09:39:20.00Z <<<

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


The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do 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: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.

We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

Get Noticed on the Internet! Increase visibility for this domain name by listing it at www.whoisbusinesslistings.com

  REGISTRAR ENOM, INC.

  REFERRER http://www.enom.com

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =pu-gh.com

  PORT 43

  SERVER whois.enom.com

  ARGS pu-gh.com

  PORT 43

  TYPE domain

DOMAIN

  NAME pu-gh.com

NSERVER

  NS1.3V0.NET 185.11.240.142

  NS2.3V0.NET 162.243.97.91

  NS3.3V0.NET 95.85.55.6

  NS4.3V0.NET 95.85.51.164

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

  CHANGED 2017-03-02

  CREATED 2007-01-07

  EXPIRES 2018-01-07

  REGISTERED yes

Go to top

Mistakes


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

  • www.upu-gh.com
  • www.7pu-gh.com
  • www.hpu-gh.com
  • www.kpu-gh.com
  • www.jpu-gh.com
  • www.ipu-gh.com
  • www.8pu-gh.com
  • www.ypu-gh.com
  • www.pu-ghebc.com
  • www.pu-ghebc.com
  • www.pu-gh3bc.com
  • www.pu-ghwbc.com
  • www.pu-ghsbc.com
  • www.pu-gh#bc.com
  • www.pu-ghdbc.com
  • www.pu-ghfbc.com
  • www.pu-gh&bc.com
  • www.pu-ghrbc.com
  • www.urlw4ebc.com
  • www.pu-gh4bc.com
  • www.pu-ghc.com
  • www.pu-ghbc.com
  • www.pu-ghvc.com
  • www.pu-ghvbc.com
  • www.pu-ghvc.com
  • www.pu-gh c.com
  • www.pu-gh bc.com
  • www.pu-gh c.com
  • www.pu-ghgc.com
  • www.pu-ghgbc.com
  • www.pu-ghgc.com
  • www.pu-ghjc.com
  • www.pu-ghjbc.com
  • www.pu-ghjc.com
  • www.pu-ghnc.com
  • www.pu-ghnbc.com
  • www.pu-ghnc.com
  • www.pu-ghhc.com
  • www.pu-ghhbc.com
  • www.pu-ghhc.com
  • www.pu-gh.com
  • www.pu-ghc.com
  • www.pu-ghx.com
  • www.pu-ghxc.com
  • www.pu-ghx.com
  • www.pu-ghf.com
  • www.pu-ghfc.com
  • www.pu-ghf.com
  • www.pu-ghv.com
  • www.pu-ghvc.com
  • www.pu-ghv.com
  • www.pu-ghd.com
  • www.pu-ghdc.com
  • www.pu-ghd.com
  • www.pu-ghcb.com
  • www.pu-ghcom
  • www.pu-gh..com
  • www.pu-gh/com
  • www.pu-gh/.com
  • www.pu-gh./com
  • www.pu-ghncom
  • www.pu-ghn.com
  • www.pu-gh.ncom
  • www.pu-gh;com
  • www.pu-gh;.com
  • www.pu-gh.;com
  • www.pu-ghlcom
  • www.pu-ghl.com
  • www.pu-gh.lcom
  • www.pu-gh com
  • www.pu-gh .com
  • www.pu-gh. com
  • www.pu-gh,com
  • www.pu-gh,.com
  • www.pu-gh.,com
  • www.pu-ghmcom
  • www.pu-ghm.com
  • www.pu-gh.mcom
  • www.pu-gh.ccom
  • www.pu-gh.om
  • www.pu-gh.ccom
  • www.pu-gh.xom
  • www.pu-gh.xcom
  • www.pu-gh.cxom
  • www.pu-gh.fom
  • www.pu-gh.fcom
  • www.pu-gh.cfom
  • www.pu-gh.vom
  • www.pu-gh.vcom
  • www.pu-gh.cvom
  • www.pu-gh.dom
  • www.pu-gh.dcom
  • www.pu-gh.cdom
  • www.pu-ghc.om
  • www.pu-gh.cm
  • www.pu-gh.coom
  • www.pu-gh.cpm
  • www.pu-gh.cpom
  • www.pu-gh.copm
  • www.pu-gh.cim
  • www.pu-gh.ciom
  • www.pu-gh.coim
  • www.pu-gh.ckm
  • www.pu-gh.ckom
  • www.pu-gh.cokm
  • www.pu-gh.clm
  • www.pu-gh.clom
  • www.pu-gh.colm
  • www.pu-gh.c0m
  • www.pu-gh.c0om
  • www.pu-gh.co0m
  • www.pu-gh.c:m
  • www.pu-gh.c:om
  • www.pu-gh.co:m
  • www.pu-gh.c9m
  • www.pu-gh.c9om
  • www.pu-gh.co9m
  • www.pu-gh.ocm
  • www.pu-gh.co
  • pu-gh.comm
  • www.pu-gh.con
  • www.pu-gh.conm
  • pu-gh.comn
  • www.pu-gh.col
  • www.pu-gh.colm
  • pu-gh.coml
  • www.pu-gh.co
  • www.pu-gh.co m
  • pu-gh.com
  • www.pu-gh.cok
  • www.pu-gh.cokm
  • pu-gh.comk
  • www.pu-gh.co,
  • www.pu-gh.co,m
  • pu-gh.com,
  • www.pu-gh.coj
  • www.pu-gh.cojm
  • pu-gh.comj
  • www.pu-gh.cmo
Show All Mistakes Hide All Mistakes