boelter.blog | boelter.blog | Tobias Boelter’s

Robots.txt Information

Robot	Path	Permission
GoogleBot	/	✔
BingBot	/	✔
BaiduSpider	/	✔
YandexBot	/	✔
User-agent: * Disallow: /wp-admin/ Allow:

Meta Tags

Title	boelter.blog \| Tobias Boelter’s
Description	boelter.blog Tobias Boelter’s Blog Menu Home about me publications Where to store your auth token? Cookie or JS? Both! In the security community, there is
Keywords	N/A

Server Information

WebSite	boelter.blog
Host IP	104.21.96.89
Location	United States

Related Websites

                        Site
                        Rank
                    

More to Explore

boelter.blog Valuation

US$381,869

Last updated: 2023-05-09 16:43:31

boelter.blog has Semrush global rank of 27,717,122. boelter.blog has an estimated worth of US$ 381,869, based on its estimated Ads revenue. boelter.blog receives approximately 44,062 unique visitors each day. Its web server is located in United States, with IP address 104.21.96.89. According to SiteAdvisor, boelter.blog is safe to visit.

Traffic & Worth Estimates

Purchase/Sale Value	US$381,869
Daily Ads Revenue	US$353
Monthly Ads Revenue	US$10,575
Yearly Ads Revenue	US$126,898
Daily Unique Visitors	2,938
Note: All traffic and earnings values are estimates.

DNS Records

Host	Type	TTL	Data
boelter.blog.	A	299	IP: 104.21.96.89
boelter.blog.	A	299	IP: 172.67.176.67
boelter.blog.	AAAA	299	IPV6: 2606:4700:3037::6815:6059
boelter.blog.	AAAA	299	IPV6: 2606:4700:3034::ac43:b043
boelter.blog.	NS	86400	NS Record: chris.ns.cloudflare.com.
boelter.blog.	NS	86400	NS Record: ingrid.ns.cloudflare.com.
boelter.blog.	MX	300	MX Record: 0 mail.b2b-host.de.
boelter.blog.	TXT	300	TXT Record: v=spf1 mx a -all

HtmlToTextCheckTime:2023-05-09 16:43:31

boelter.blog Tobias Boelter’s Blog Menu Home about me publications Where to store your auth token? Cookie or JS? Both! In the security community, there is a contention on whether an auth token (think OAuth access_token, JSESSIONID, ...) should be stored inside a cookie or if should live within javascript, so e.g. a variable in a single page application, local storage or session storage, etc. If it is stored in javascript, all requests to resources that require auth have to be made from JS, so it is usually difficult to retrofit an application that was written for cookie-based auth to have it store the auth token in JS. That being said, for new applications, the developers have to make this decision. Which one is more secure? It is often said that cookies are safer against XSS (with the HttpOnly flag set), but using cookies makes your app more vulnerable to CSRF. Tokens within JS, on the other hand, are easier to exfiltrate through XSS but CSRF therefore becomes much less of a problem.

HTTP Headers

HTTP/1.1 301 Moved Permanently
Date: Mon, 01 Nov 2021 04:59:26 GMT
Connection: keep-alive
Cache-Control: max-age=3600
Expires: Mon, 01 Nov 2021 05:59:26 GMT
Location: https://boelter.blog/
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=p6ASAshNAQ2LgMVbsw62JzkoxdFHKsYo7A1DdrOWaXd1%2F4h99fXvl1rFOnfxEY1czUqFUqmF%2Folfe3am7dfN5XzqaQofr6QVbYUXnKAsUYy26e%2Fb6X%2BA9UevUxMgEgg%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 6a728dc0db6e616e-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: Mon, 01 Nov 2021 04:59:26 GMT
content-type: text/html; charset=UTF-8
x-powered-by: PHP/5.6.39
link: ; rel="https://api.w.org/"
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=608sZR5JsEcz1F1AnIPU4lIlbbd2cJwzVlJz3Omkg7oW0PwfinQ4WjyQiIAe%2B%2BctrJm3IbbTciot3G5pQgyy4LnHjlTEH%2BM%2BvU0g%2B2guNiddRCTBgGWquv3h6hZeSgY%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 6a728dc11b33630c-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

boelter.blog Whois Information

Domain Name: BOELTER.BLOG
Registry Domain ID: D153118736-CNIC
Registrar WHOIS Server: whois.domrobot.com
Registrar URL: https://inwx.com
Updated Date: 2021-04-14T08:02:59.0Z
Creation Date: 2019-12-18T00:28:18.0Z
Registry Expiry Date: 2021-12-18T23:59:59.0Z
Registrar: INWX GmbH & Co. KG
Registrar IANA ID: 1420
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Country: DE
Name Server: CHRIS.NS.CLOUDFLARE.COM
Name Server: INGRID.NS.CLOUDFLARE.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@inwx.de
Registrar Abuse Contact Phone: +49.309832120
>>> Last update of WHOIS database: 2021-09-19T14:24:22.0Z <<<

boelter.blog valuation and analysis