anubhavranjan.me valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title Anubhav Ranjan | Software Engineer II at
Description Update Property in a Nested Array of entities in Anubhav Ranjan Technical Advisor at Microsoft Anubhav Ranjan --> Update Property in a Nested Array of entities in MongoDB Many of us would have already
Keywords N/A
Server Information
WebSite anubhavranjan faviconanubhavranjan.me
Host IP 172.67.193.100
Location United States
Related Websites
Site Rank
More to Explore
anubhavranjan.me Valuation
US$968,828
Last updated: 2023-05-01 04:25:07

anubhavranjan.me has Semrush global rank of 10,924,858. anubhavranjan.me has an estimated worth of US$ 968,828, based on its estimated Ads revenue. anubhavranjan.me receives approximately 111,788 unique visitors each day. Its web server is located in United States, with IP address 172.67.193.100. According to SiteAdvisor, anubhavranjan.me is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$968,828
Daily Ads Revenue US$895
Monthly Ads Revenue US$26,830
Yearly Ads Revenue US$321,949
Daily Unique Visitors 7,453
Note: All traffic and earnings values are estimates.
DNS Records
Host Type TTL Data
anubhavranjan.me. A 299 IP: 172.67.193.100
anubhavranjan.me. A 299 IP: 104.21.60.71
anubhavranjan.me. AAAA 299 IPV6: 2606:4700:3033::ac43:c164
anubhavranjan.me. AAAA 299 IPV6: 2606:4700:3030::6815:3c47
anubhavranjan.me. NS 86400 NS Record: nina.ns.cloudflare.com.
anubhavranjan.me. NS 86400 NS Record: nikon.ns.cloudflare.com.
HtmlToTextCheckTime:2023-05-01 04:25:07
Anubhav Ranjan Technical Advisor at Microsoft Anubhav Ranjan --> Update Property in a Nested Array of entities in MongoDB Many of us would have already used MongoDB for storing data as Documents. However, I come from a world of SQL where everything is stored in Tables following the Normalization process. Hence, anything that can be further broken down, should be considered storing in a separate table. In the world of MongoDB or rather, No-SQL, we do not have anything like that. Here, the more connected the data is supposed to have, the more chances of storing them together makes sense. Let’s look at the below example: { "_id":"d5ebb427", "name":"Anubhav Ranjan", "email":" [email protected] ", "subscriptions":[ { "subscriptionId":"1abc", "showId":"d060b8ca", "notificationEnabled":true }, { "subscriptionId":"2abc", "showId":"d060b8cb", "notificationEnabled":true } ] } Let’s consider the code snippet above. I have an object User having Two Subscriptions. Now I want to make one of the
Ads.txtCheckTime:2023-05-01 04:25:07
google.com, pub-8580778989136795, DIRECT,
HTTP Headers
HTTP/1.1 301 Moved Permanently
Date: Sat, 23 Oct 2021 20:26:22 GMT
Content-Type: text/html
Connection: keep-alive
location: https://www.anubhavranjan.me/
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=XtSmnE1kc2veTozzxsn8Uf%2FYAat4DQ2P8WZbGx0GUwzL6GKDd9wG2eRowPrd%2BM%2F5i81Q05CDC%2Fa5HE4%2FE03uZUvF4P7VLBignqG8ac7yu609itMtL1w3Y56bVqFNTOFWvXJl"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 6a2db32f98452958-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

HTTP/2 200 
date: Sat, 23 Oct 2021 20:26:22 GMT
content-type: text/html; charset=UTF-8
link: ; rel="https://api.w.org/"
link: ; rel=shortlink
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=a43JEH7ihdjoJQxwGHcLyLJNubDn%2FXRfaNdG%2F8Wh%2FIj%2FKiwPTTc9rIvu089OY7A%2FTGWOxS58SOIAdqGz%2FfbCklW8TQv7ZJ6%2BR2XirhN7ZPTzz%2FMxWaqaJE9aEfhOZQP4aO68ey%2BFuQ%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 6a2db3316a35291f-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400
anubhavranjan.me Whois Information
Domain Name: ANUBHAVRANJAN.ME
Registry Domain ID: D108500000016882306-AGRS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2020-09-10T07:04:53Z
Creation Date: 2015-10-12T19:20:34Z
Registry Expiry Date: 2021-10-12T19:20:34Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant State/Province: Delhi
Registrant Country: IN
Name Server: NS1.DIGITALOCEAN.COM
Name Server: NS2.DIGITALOCEAN.COM
Name Server: NS3.DIGITALOCEAN.COM
DNSSEC: unsigned
>>> Last update of WHOIS database: 2021-09-12T06:06:23Z <<<