vigneshmurugesan.com valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
User-agent: Mediapartners-Google Disallow: User-agent: * Disallow: /search Allow: / Sitemap: | ||
Meta Tags
| Title | Vignesh Murugesan’s |
| Description | This is Vignesh Murugesan’s blog about thoughts on latest technologies and engineering |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 216.239.36.21 |
| Location | United States |
Related Websites
| Site | Rank |
More to Explore
vigneshmurugesan.com Valuation
|
US$955
Last updated: 2023-05-12 08:19:52
vigneshmurugesan.com has Semrush global rank of 0. vigneshmurugesan.com has an estimated worth of US$ 955, based on its estimated Ads revenue. vigneshmurugesan.com receives approximately 110 unique visitors each day. Its web server is located in United States, with IP address 216.239.36.21. According to SiteAdvisor, vigneshmurugesan.com is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$955 |
| Daily Ads Revenue | US$0 |
| Monthly Ads Revenue | US$26 |
| Yearly Ads Revenue | US$317 |
| Daily Unique Visitors | 7 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| vigneshmurugesan.com. | A | 3600 | IP: 216.239.36.21 |
| vigneshmurugesan.com. | A | 3600 | IP: 216.239.34.21 |
| vigneshmurugesan.com. | A | 3600 | IP: 216.239.32.21 |
| vigneshmurugesan.com. | A | 3600 | IP: 216.239.38.21 |
| vigneshmurugesan.com. | AAAA | 3600 | IPV6: 2001:4860:4802:36::15 |
| vigneshmurugesan.com. | AAAA | 3600 | IPV6: 2001:4860:4802:38::15 |
| vigneshmurugesan.com. | AAAA | 3600 | IPV6: 2001:4860:4802:32::15 |
| vigneshmurugesan.com. | AAAA | 3600 | IPV6: 2001:4860:4802:34::15 |
| vigneshmurugesan.com. | NS | 21600 | NS Record: ns-cloud-c4.googledomains.com. |
| vigneshmurugesan.com. | NS | 21600 | NS Record: ns-cloud-c2.googledomains.com. |
| vigneshmurugesan.com. | NS | 21600 | NS Record: ns-cloud-c1.googledomains.com. |
| vigneshmurugesan.com. | NS | 21600 | NS Record: ns-cloud-c3.googledomains.com. |
| vigneshmurugesan.com. | MX | 3600 | MX Record: 40 alt4.gmr-smtp-in.l.google.com. |
| vigneshmurugesan.com. | MX | 3600 | MX Record: 20 alt2.gmr-smtp-in.l.google.com. |
| vigneshmurugesan.com. | MX | 3600 | MX Record: 30 alt3.gmr-smtp-in.l.google.com. |
| vigneshmurugesan.com. | MX | 3600 | MX Record: 5 gmr-smtp-in.l.google.com. |
| vigneshmurugesan.com. | MX | 3600 | MX Record: 10 alt1.gmr-smtp-in.l.google.com. |
HtmlToTextCheckTime:2023-05-12 08:19:52
| Vignesh Murugesan’s Blog Thoughts; Tips; Hacks; .*; Monday, February 18, 2019 GraphQL GraphQL What is GraphQL It is a specification laid out by Facebook which proposed an alternative way to query and modify data. Think of it is an as a complimentary of REST/RPC. Now head here and read the original graphQL documentation . It will take 2-3 hours tops but is a worthy read. This will help you build some impressions on it and help contrast against mine below: Why use GraphQL Core advantage Instead of defining custom backend rpc/rest endpoints for every data-shape, graphql allows you to build a more general endpoint which give frontend/mobile engineers freedom and query and play with the data. It might be less efficient, add a bit more complexity (need for things like data-loader ), harder to standardize and control client-contracts for. What it looses in complexity and control, it gains in flexibility and freedom - provided your data model is worth of a graphql-ish query How to tell if my |
HTTP Headers
HTTP/1.1 301 Moved Permanently Location: http://www.vigneshmurugesan.com/ Date: Thu, 09 Dec 2021 08:56:58 GMT Content-Type: text/html; charset=UTF-8 Server: ghs Content-Length: 229 X-XSS-Protection: 0 X-Frame-Options: SAMEORIGIN HTTP/1.1 301 Moved Permanently Location: https://www.vigneshmurugesan.com/ Content-Type: text/html; charset=UTF-8 Date: Thu, 09 Dec 2021 08:56:58 GMT Expires: Thu, 09 Dec 2021 08:56:58 GMT Cache-Control: private, max-age=0 X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self' X-XSS-Protection: 1; mode=block Server: GSE Transfer-Encoding: chunked Accept-Ranges: none Vary: Accept-Encoding HTTP/2 200 content-type: text/html; charset=UTF-8 expires: Thu, 09 Dec 2021 08:56:58 GMT date: Thu, 09 Dec 2021 08:56:58 GMT cache-control: private, max-age=0 last-modified: Sun, 05 Dec 2021 02:53:06 GMT etag: W/"a2c2c902938f92e32fcd578f07653d6e03befcfd585f3cf81d0d947a1d211946" x-content-type-options: nosniff x-xss-protection: 1; mode=block content-length: 0 server: GSE |
vigneshmurugesan.com Whois Information
Domain Name: VIGNESHMURUGESAN.COM Registry Domain ID: 1697518459_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.google.com Registrar URL: http://domains.google.com Updated Date: 2021-01-18T07:28:53Z Creation Date: 2012-01-18T03:04:20Z Registry Expiry Date: 2022-01-18T03:04:20Z Registrar: Google LLC Registrar IANA ID: 895 Registrar Abuse Contact Email: registrar-abuse@google.com Registrar Abuse Contact Phone: +1.8772376466 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: NS-CLOUD-C1.GOOGLEDOMAINS.COM Name Server: NS-CLOUD-C2.GOOGLEDOMAINS.COM Name Server: NS-CLOUD-C3.GOOGLEDOMAINS.COM Name Server: NS-CLOUD-C4.GOOGLEDOMAINS.COM DNSSEC: unsigned >>> Last update of whois database: 2021-12-09T07:29:56Z <<< |