marklunds.com valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title Peter Marklund’s
Description Pages Home CV Linkedin Twitter Github Contact Peter Marklund’s Home Peter on Software Lessons Learned in software and web development Subscribe 2022-06-29
Keywords N/A
Server Information
WebSite marklunds faviconmarklunds.com
Host IP 54.220.192.176
Location Ireland
Related Websites
Site Rank
More to Explore
marklunds.com Valuation
US$2,029,846
Last updated: 2023-05-12 11:36:56

marklunds.com has Semrush global rank of 5,214,340. marklunds.com has an estimated worth of US$ 2,029,846, based on its estimated Ads revenue. marklunds.com receives approximately 234,213 unique visitors each day. Its web server is located in Ireland, with IP address 54.220.192.176. According to SiteAdvisor, marklunds.com is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$2,029,846
Daily Ads Revenue US$1,874
Monthly Ads Revenue US$56,212
Yearly Ads Revenue US$674,534
Daily Unique Visitors 15,615
Note: All traffic and earnings values are estimates.
DNS Records
Host Type TTL Data
marklunds.com. A 3599 IP: 54.220.192.176
marklunds.com. A 3599 IP: 46.137.15.86
marklunds.com. A 3599 IP: 54.73.53.134
marklunds.com. NS 3600 NS Record: ns1.dnsimple.com.
marklunds.com. NS 3600 NS Record: ns2.dnsimple.com.
marklunds.com. NS 3600 NS Record: ns3.dnsimple.com.
marklunds.com. NS 3600 NS Record: ns4.dnsimple.com.
marklunds.com. MX 3600 MX Record: 10 in1-smtp.messagingengine.com.
marklunds.com. MX 3600 MX Record: 20 in2-smtp.messagingengine.com.
marklunds.com. TXT 3600 TXT Record: v=spf1 include:spf.messagingengine.com ~all
marklunds.com. TXT 3600 TXT Record: ALIAS for marklunds.herokuapp.com
HtmlToTextCheckTime:2023-05-12 11:36:56
Pages Home CV Linkedin Twitter Github Contact Peter Marklund’s Home Peter on Software Lessons Learned in software and web development Subscribe 2022-06-29T12:00:40.106Z Realtime Replication of CMS Data from MongoDB to S3 I’ve been doing an interesting project at work where we replicate (sync) data in realtime (with say 200 ms latency) from our CMS database (MongoDB) to file storage (AWS S3). The motivation for doing this is to achieve higher reliability/uptime and scalability than you would typically achieve with a REST API in front of a database like MongoDB or Postgres. For our use case a typical CDN setup with a 60 second TTL (Cloudwatch in our case) in front of the API didn’t fulfill our requirements and didn’t get us good cache hit rate. I think using something like Varnish/Fastly where you set a long (or even infinite) TTL and expire the cache when data changes and/or are able to have the CDN serve stale (i.e. using stale-while-revalidate, stale-if-error Cache-Control
HTTP Headers
HTTP/1.1 404 Not Found
Server: Cowboy
Connection: keep-alive
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization,Content-Type,Accept,Origin,User-Agent,DNT,Cache-Control,X-Mx-ReqToken,Keep-Alive,X-Requested-With,If-Modified-Since,X-CSRF-Token
Access-Control-Allow-Methods: GET,POST,PUT,PATCH,DELETE,OPTION
Access-Control-Allow-Origin: *
Cache-Control: public, max-age=undefined
Date: Wed, 15 Dec 2021 09:05:28 GMT
Via: 1.1 vegur
marklunds.com Whois Information
Domain Name: MARKLUNDS.COM
Registry Domain ID: 95946443_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enomdomains.com
Updated Date: 2021-02-18T08:23:57Z
Creation Date: 2003-03-19T15:46:29Z
Registry Expiry Date: 2022-03-19T14:46:29Z
Registrar: eNom, LLC
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.DNSIMPLE.COM
Name Server: NS2.DNSIMPLE.COM
Name Server: NS3.DNSIMPLE.COM
Name Server: NS4.DNSIMPLE.COM
DNSSEC: unsigned
>>> Last update of whois database: 2021-12-15T08:34:27Z <<<