grg.pw Report : Visit Site

Technical data of the grg.pw

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host grg.pw. Currently, hosted in United Kingdom and its service provider is Linode LLC .

the related websites

grg.org.uk grg.grimaldi.co.uk lse.co.uk link.springer.com cleeve-weather.grg.org.uk mymbtraining.grg.com grgcolumncasings.co.uk rbs-grgbusinessactiongroup.org st-dunstans.org bbc.co.uk mydavidwilsonhome.co.uk bookworldws.co.uk mini-itx.com telegraph.co.uk surveyorsequipment.co.uk storybookcastle.com freeport-talke.com bridalmanor.co.za 

HTTP Header Analysis

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

DNS

HtmlToText

toggle navigation giorgio (grg) bonfiglio home about me contact giorgio (grg) bonfiglio cloud evangelist, systems/network engineer customer experience and discrimination on gumtree customer experience and discrimination on gumtree 05/05/2018 giorgio bonfiglio comments 1 comment in a world where customer experience is key, gumtree, the leading online classifieds website in england, is telling me to f*ck off. something that i will do indeed as their tos are crystal clear (they can restrict access with no explanation due), but not without telling the story first. it all started this morning: after having signed up using my 10 years old google account and my real name (which, even if i’m not donald trump, should have a decent reputation and trust online) i posted an ad for my hp dl320e (and even paid to have it featured). location was my real postcode (which you can verify in public records) and i paid with an uk credit card (just another way for them to verify my identity). good experience up to that point: nice and easy ui, clean workflow. the ad went into moderation queue, but after a while it moved straight into the “removed” state: allegedly, i’ve broken some posting rules and should have expected an email with some explanations. except the email never came in (no, it’s not my spam filter, i got other emails from them) and the link to the posting rules leads to a blank page (there is a menu on the left, but every single item leads to a blank page). i asked for support on twitter, genuinely thinking it should have been a mistake of some automated fraud prevention system (a very cheap one, probably): nice start. my first ad on @gumtree (#1297572744) was removed because it breaks an unspecified rule. no additional details, no emails to explain. @helpmegumtree — giorgio bonfiglio (@g_bonfiglio) may 5, 2018 the only thing i managed to get back was this response via dm, which classifies as the worst and unnecessarily rude answer i ever got from someone’s customer care department: i tried to appeal by sending an email to their support department, hoping for a deeper review and consideration. and it happened: someone came back to me apologising and explaining that my ad and account were absolutely fine, no rule had been broken and that the block was the result of a mistake. it would have been lifted immediately. the end of an odyssey, you would think. well, no: two hours later my account got blocked again, and this email landed in my mailbox: in short, i’m now permanently banned. they won’t tell me why and won’t answer any further query on the matter. i would love to dig and figure out what’s wrong, but i’m in front of a brick wall. let me make a couple of assumptions: i’ve been blocked before having published my first ad, so i can’t have been reported by other users. the only things gumtree knows about me are: my full name my email address where i live my credit card details we already have a word for when you are denied something based on those four parameters: discrimination – and this is what’s happening here. if anybody from gumtree wants to get in touch and explain feel free, you have my contact details. share this: google facebook twitter linkedin email like this: like loading... telegram’s infrastructure and outages. some updates. telegram’s infrastructure and outages. some updates. 29/04/2018 giorgio bonfiglio comments 0 comment this post is meant as an (ongoing) sequence of updates to the previous one about telegram’s outages in march and april 2018. please read it here first. last updated: april 30th, 6:00 am utc update 1 with the help of a friend (and his own howisresolved ), we managed to confirm that for most open resolvers worldwide (25k+ tested) api.telegram.org is showing up as 149.154.167.220. only outliers seem to be china (resolving as of now as 174.37.154.236) and russia (85.142.29.248). update 2 during my analysis this morning i created a new telegram app, and the (only) suggested mtproto (the telegram protocol) server was 149.154.167.50. this falls into the ip range analysed above, and seems to be solely located in amsterdam. kipters was so kind to review and help me notice that this server is not used for real “data” communication, but just for a “discovery” api call ( help.getconfig method) which will return the list of servers that will have to be used for sending messages. we are currently still in process of comparing ranges received across the world, but in the best case scenario (ie: they are spread over multiple geographic locations) this would mean that there is still a single point of failure in the hardcoded “directory” server. update 3 what i found in the previous note was “too weird to be true”, so i went ahead and kept digging into tdlib and the official desktop and android apps, to confirm wether they were bootstrapping a session beginning from a single mtproto endpoint or not. fortunately, turns out this is not the case (relevant snippets for tdlib , desktop , android apps): both of them contain, hardcoded, in addition to endpoints in the range 149.154.167.0/24 (amsterdam, as62041), endpoints in 149.154.175.0/24 (miami, as59930) and 149.154.171.0/24 (singapore, as62014). sounds like we should look into different reasons why many users worldwide outside of emea had issues today (or wait for an official, detailed post mortem if it will ever come): there are many, from broken dependencies to weird cases of mis-routing. some areas are left to explore (feel free to share your ideas if you have any): why third party apps don’t have access to the whole list of “initial” mtproto endpoints, and are pushed to use only a single, non redundant one? why the main website and api.telegram.org (mainly used for bots i think) are based off a single location? update 4 telegram web ( https://web.telegram.org/ ) seems to be single-homed in amsterdam too. as i haven’t had the opportunity to test during the outage, i don’t know whether it has been failed over somewhere else or not. update 5 according to the official documentation , users (registered by phone number) are located off a single datacenter, picked at signup time based on geographical proximity: “ during the process of working with the api, user information is accumulated in the dc with which the user is associated. this is the reason a user cannot be associated with a different dc by means of the client. ” they are only moved if they keep connecting from a remote location for a prolonged period of time (ie: you permanently relocate to another continent): this might explain why there seem to be no failover scenario and 12+ hours outages are happening. (thanks to adjustableneutralism from reddit for flagging) share this: google facebook twitter linkedin email like this: like loading... telegram is down (again): a deep look at their infrastructure. telegram is down (again): a deep look at their infrastructure. 29/04/2018 giorgio bonfiglio comments 0 comment i’ve been a strong telegram advocate since its launch in 2013, mainly because of the advanced features and technical state of the art compared to competitors – as a consequence, i’ve been looking very closely at their infrastructure for the last few years. the two large scale outages that recently hit their users and the sequence of events following them made me ask some questions around their platform. for most of them i have only found additional question marks rather than answers, but here it is what i have so far. let’s start from the outages: in case you missed that, on march 29th and april 29th this year, telegram went down in their amsterdam datacenter due to a power failure, causing disruptions, according to their official communications, to users in emea, mena, russia and cis. power outage at a @telegram server cluster causing issues in europe. working to fix it from our side, but a lot depends on when the datacenter provider puts the power equipment in order. — pavel durov (@durov) march 29, 2018 repairs are ongoing a

URL analysis for grg.pw

https://grg.pw/2018/05/customer-experience-and-discrimination-on-gumtree/#comments
https://grg.pw/page/2/
https://grg.pw/2017/10/me-and-hp-a-bare-metal-odissey/
https://grg.pw/2018/04/telegram-is-down-again-a-deep-look-at-their-infrastructure/?share=facebook
https://grg.pw/2018/05/customer-experience-and-discrimination-on-gumtree/?share=email
https://grg.pw/2017/11/eventi-straordinari-e-siti-istituzionali-un-rapporto-ancora-tormentato/#respond
https://grg.pw/2018/04/telegram-is-down-again-a-deep-look-at-their-infrastructure/?share=twitter
https://grg.pw/2017/07/dont-buy-servers/
https://grg.pw/2018/04/telegram-is-down-again-a-deep-look-at-their-infrastructure/?share=linkedin
https://grg.pw/2018/05/customer-experience-and-discrimination-on-gumtree/?share=twitter
https://grg.pw/2018/04/this-is-your-sysadmin-speaking-please-expect-some-turbulence/?share=google-plus-1
https://grg.pw/about-me/
https://grg.pw/wp-content/2018/04/img_1732.jpg
https://grg.pw/2018/04/telegrams-infrastructure-and-outages-some-updates/?share=facebook
https://grg.pw/2018/04/this-is-your-sysadmin-speaking-please-expect-some-turbulence/#respond

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;

SERVERS

  SERVER pw.whois-servers.net

  ARGS grg.pw

  PORT 43

DOMAIN

NSERVER

  NS-209-C.GANDI.NET 217.70.179.2

  NS-236-A.GANDI.NET 173.246.98.2

  NS-112-B.GANDI.NET 213.167.229.2

Mistakes

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