+
@@ -80,9 +81,9 @@
{:else}
-
diff --git a/src/lib/SideMenu.svelte b/src/lib/SideMenu.svelte
index fbb4926..0bcb2ac 100644
--- a/src/lib/SideMenu.svelte
+++ b/src/lib/SideMenu.svelte
@@ -28,6 +28,7 @@
Home
About us
FAQ
+
Blogs
{#if auth.isAuthenticated}
diff --git a/src/lib/posts/dns-records-for-email-servers-explained-with-practical-examples.md b/src/lib/posts/dns-records-for-email-servers-explained-with-practical-examples.md
new file mode 100644
index 0000000..ef6140b
--- /dev/null
+++ b/src/lib/posts/dns-records-for-email-servers-explained-with-practical-examples.md
@@ -0,0 +1,107 @@
+---
+title: Essential DNS records for mailservers explained
+subtitle: How to set up all essential DNS records for reliable mail delivery
+description: Learn which DNS records are required for a functional mailserver, how to configure them, and get best-practice tips for A, AAAA, MX, SPF, DKIM, and DMARC records.
+---
+
+# All DNS records needed for a functional mailserver
+
+Setting up your own mailserver can sound intimidating, but ensuring the right Domain Name System (DNS) records are in place is essential for making sure emails are delivered and not rejected or flagged as spam.
+
+Here, we’ll walk through every DNS record type that’s necessary and relevant security records for a reliable and standards-compliant mail system.
+
+## A and AAAA records: pointing to your mailserver
+
+**A records** (Address records) map a domain or subdomain to an IPv4 address, while **AAAA records** do the same for IPv6 addresses. These are crucial, as the server where your mailserver runs must have its address resolvable.
+
+Example A record:
+```
+mx.example.hexname.com. A 198.51.100.42
+```
+Example AAAA record:
+```
+mx.example.hexname.com. AAAA 2001:db8:abcd:1234::42
+```
+Tips:
+- Use `mx.example.hexname.com` (not your root domain) to separate mailserver traffic.
+- For better compatability, use both A and AAAA records.
+
+## MX records: announcing where to deliver email
+
+**MX records** (Mail Exchanger records) specify which hosts should receive email for your domain. The record includes a priority (lower numbers mean higher priority) and points to a hostname that must have an A or AAAA record.
+
+Example MX record:
+```
+example.hexname.com. MX 10 mx.example.hexname.com.
+```
+- Use only hostnames (like `mx.example.hexname.com`), never direct IPs, for the value.
+- You can set multiple MX records with varying priority for failover. This ensures that if your primary mailserver has downtime, the second one can take over.
+
+> Having a backup mailserver is not *so* important since email implements retries with incremental backoffs. So if a delivery to your one and only mailserver fails, it will be retried over the course of the day and the week.
+
+## TXT records: SPF, DKIM, and DMARC
+
+TXT records can be used for pretty much anything. Here they're used in critical mail authentication methods: SPF, DKIM, and DMARC. These reduce spam and prevent spoofing.
+
+### Sender Policy Framework (SPF)
+
+SPF specifies which mailservers are authorized to send for your domain. This is useful if you're allowing other mailservers to send mail on your behalf for deliverability/marketing reasons.
+
+Its value is placed in a TXT record:
+
+```
+example.hexname.com. TXT "v=spf1 a mx -all"
+```
+Meaning:
+- `a` allows the A/AAAA IPs of `example.hexname.com` to send emails
+- `mx` allows the MX servers for the domain (so, `mx.example.hexname.com`)
+- `-all` means "fail if the previous conditioned didn't match"
+
+> A domain can only have one SPF TXT record. The rest will be ignored.
+
+### DomainKeys Identified Mail (DKIM)
+
+DKIM lets your server sign outgoing emails with a cryptographic key, which recipients can verify via a public key published in your DNS (DKIM).
+
+The exact steps for acquiring the record depend on your mail software, but here is a general example:
+
+```
+default._domainkey.example.hexname.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkq..."
+```
+- `default` is the selector and can be any word set by your mailserver config
+- The `p=` value is your public key
+
+You can often find DKIM keys and setup instructions in your mailserver's admin panel, or CLI tools.
+
+### Domain-based Message Authentication, Reporting, and Conformance (DMARC)
+
+DMARC tells receiving mailservers how to handle mail that fails SPF, DKIM, or both, and can provide reporting to help you discover misconfigurations.
+
+An example of a strong DMARC policy is:
+```
+_dmarc.example.hexname.com. TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.hexname.com"
+```
+- `p=reject` can also be `none` (for testing) or `quarantine` (to send the failing emails into quarantine).
+- `rua=` specifies an email address for DMARC aggregate reports. The recipient is usually not a person, but rather an automated service that provides reports in a human-readable format.
+
+> DMARC reports usually arrive as XML file attachments, therefore they're hard to parse by humans. Plenty of free tools exist like [Cloudflare DMARC Management](https://developers.cloudflare.com/dmarc-management/) or [Postmark](https://dmarc.postmarkapp.com/) that send you summaries of the aggregate reports.
+
+## Filling your DNS records
+
+If using a DNS service like
HexName.com, you can register a subdomain (like `example.hexname.com`), create an `mx` record (such as `mx.example.hexname.com`), and add the above A, AAAA, MX, and TXT records. Ensure each record is entered precisely.
+
+A complete (minimal) set for secure mail delivery:
+- A/AAAA records pointing to your mailserver's IP
+- MX record on `example.hexname.com` pointing to `mx.example.hexname.com`
+- SPF TXT on `example.hexname.com` with the contents `"v=spf1 a mx -all"`
+- DKIM TXT on `default._domainkey.example.hexname.com`
+- DMARC TXT on `_dmarc.example.hexname.com` with the contents `v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.hexname.com`
+
+These records ensure your mail can both arrive and be accepted by most of the world.
+
+Many free online "mailserver tester" tools exist, letting you double-check your mailserver configuration. Our recommendations are:
+- [MxToolBox's SMTP diagnostic tool](https://mxtoolbox.com/diagnostic.aspx)
+- [Mail Tester](https://www.mail-tester.com/) - to check the "spammyness" of your mailserver
+- And many others!
+
+After you're done with the basics, you can look into MTA-STS, TLS reporting, SPF reporting as well as methods to help ensure decent deliverability.
diff --git a/src/lib/posts/how-mta-sts-makes-email-routing-safer-and-more-reliable.md b/src/lib/posts/how-mta-sts-makes-email-routing-safer-and-more-reliable.md
new file mode 100644
index 0000000..bf0f98b
--- /dev/null
+++ b/src/lib/posts/how-mta-sts-makes-email-routing-safer-and-more-reliable.md
@@ -0,0 +1,123 @@
+---
+title: What is MTA-STS and how to set it up effortlessly
+subtitle: Understanding MTA strict transport security and its full syntax
+description: Learn how MTA-STS works to secure email transfer. See full config syntax, real-world examples, and potential risks without it. Discover practical tips and insights for DNS and TLS reporting.
+---
+
+# What's MTA-STS, why it makes email routing safer, amd how to set it up
+
+Modern email uses Transfer Layer Security (TLS) to keep messages safe from prying eyes as they move between mail servers. But did you know that, without additional safeguards, TLS can often be bypassed? This is where Mail Transfer Agent Strict Transport Security (MTA-STS) comes in.
+
+## What is MTA-STS?
+
+MTA-STS is a standard designed to protect Simple Mail Transfer Protocol (SMTP) connections between mail servers from downgrade and Man-in-the-Middle (MitM) attacks. It enforces that inbound email for your domain is only accepted over authenticated TLS connections.
+
+Even though SMTP with STARTTLS has been around for years, it’s not foolproof - attackers can trick servers into falling back to insecure connections unless you use like MTA-STS.
+
+## How does mail transfer between servers?
+
+Email messages sent from one domain to another travel over the public internet. First, the sender's server looks up the recipient’s server using MX (Mail Exchange) records.
+
+Then, optionally, both servers attempt to establish a TLS connection using STARTTLS. Without further protection, attackers can downgrade this connection, making email transfer vulnerable.
+
+## What are the risks without MTA-STS?
+
+Without MTA-STS, email can be silently intercepted by attackers who force a connection downgrade or present fake certificates during a MitM attack. As a result your email can be read in clear text by third parties. MTA-STS ensures the sending server verifies it is using a secure, valid TLS connection, or the transition fails.
+
+## Full syntax explained
+
+The MTA-STS policy is a plain text file published at a fixed location on your web server:
+
+`https://mta-sts.example.com/.well-known/mta-sts.txt`
+
+The minimum required fields:
+
+```
+version: STSv1
+mode: enforce
+mx: mx1.example.com
+max_age: 86400
+```
+
+- `version`: Must be `STSv1`. As of now, there are no other versions.
+- `mode`: Supported values are `enforce`, `testing`, or `none`.
+- `mx`: One or more MX hostnames. Wildcards are also supported, like `*.hexname.com`.
+- `max_age`: Time in seconds for which the policy is valid (86400 is one day).
+
+You can check MTA-STS policies in the browser, e.g.:
https://mta-sts.gmail.com/.well-known/mta-sts.txt
+
+```
+version: STSv1
+mode: enforce
+mx: gmail-smtp-in.l.google.com
+mx: *.gmail-smtp-in.l.google.com
+max_age: 86400
+```
+
+## DNS record for MTA-STS
+
+A small but important TXT record in DNS tells mailservers that your domain uses MTA-STS - and which version they should check:
+
+For Gmail at `_mta-sts.gmail.com`, it looks like this:
+```
+_mta-sts.gmail.com. 300 IN TXT "v=STSv1; id=20190429T010101;"
+```
+
+The `id` can be any unique string. When you update your policy file, increment the `id` to signal other providers to fetch the new policy.
+> It's considered "best practice" to use a datetime in the `id` since it's guaranteed to be unique.
+
+## TLS reporting: get feedback on failures
+
+SMTP TLS Reporting (TLS-RPT) allows you to receive email reports if another mail server has issues delivering securely to your domain.
+
+Gmail has this record in place for `_smtp._tls.gmail.com`:
+```
+_smtp._tls.gmail.com. 300 IN TXT "v=TLSRPTv1;rua=mailto:sts-reports@google.com"
+```
+
+This means the specified email address receives reports about failed or downgraded connections, as well as successful ones.
+
+> Since the reports are in JSON, they're meant for automated reporting tools. Look up "TLS-RPT reporting" for more info.
+
+## Practical example
+
+If you host your DNS with
HexName and your mail server is `mx.example.hexname.com`. You would:
+
+1. Publish your policy at `https://mta-sts.example.hexname.com/.well-known/mta-sts.txt`, e.g.:
+
+```
+version: STSv1
+mode: enforce
+mx: mx.example.hexname.com
+max_age: 86400
+```
+
+> Hint: This can easily be done by your reverse-proxy or [Cloudflare Workers](https://developers.cloudflare.com/workers/) with this template:
+
+```
+export default {
+ async fetch(request, env, ctx) {
+ const body =
+`version: STSv1
+mode: enforce
+mx: mx.example.hexname.com
+max_age: 86400`;
+
+ return new Response(body);
+ }
+};
+```
+
+2. Add the DNS TXT record at `_mta-sts.example.hexname.com.`
+```
+_mta-sts.example.hexname.com. 3600 IN TXT "v=STSv1; id=20240612;"
+```
+
+3. Optionally, set up TLS-RPT for reporting:
+```
+_smtp._tls.example.hexname.com. 3600 IN TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.hexname.com"
+```
+
+## Summary
+
+MTA-STS is straightforward to set up but adds much-needed security to your domain’s inbound email - so no one will be sniffing your emails.
diff --git a/src/lib/posts/understanding-email-ports-modern-smtp-imap-and-jmap-usage.md b/src/lib/posts/understanding-email-ports-modern-smtp-imap-and-jmap-usage.md
new file mode 100644
index 0000000..4d1a9e5
--- /dev/null
+++ b/src/lib/posts/understanding-email-ports-modern-smtp-imap-and-jmap-usage.md
@@ -0,0 +1,81 @@
+---
+title: "All mail protocols/ports explained: SMTP, IMAP, submission, STARTTLS, JMAP"
+subtitle: A practical guide to email server ports and their specific roles
+description: This article outlines the most important email ports and protocols, explaining the purposes of each, their security implications, and how they fit into today's email infrastructure. Get practical information for configuring mail services and understanding the underlying protocols.
+---
+
+# Email protocols clarified: a modern look at SMTP, IMAP, and JMAP
+
+When configuring an email server, opening the firewall or troubleshooting delivery issues, knowledge about which ports do what is essential. This guide explains the key ports for sending and retrieving email, covers both encrypted and unencrypted traffic, and clarifies how service roles have shifted over the years.
+
+## SMTP: the backbone of email delivery
+
+SMTP (simple mail transfer protocol) forms the core of email transmission between servers and, in some cases, from clients to servers. Its role has evolved with internet standards and rising security needs.
+
+- **Port 25**: The original and still primary port for server-to-server SMTP traffic. When a message is relayed between a mailserver and a remote mail host, port 25 is used. The encryption extension STARTTLS can upgrade this connection, but is not always enforced.
+
+> Due to its abuse by spammers, many ISPs deliberately block client outbound access to port 25, making its use mostly server-exclusive today.
+
+- **Port 587**: Known as the "submission" port. Designed explicitly for end-users (email clients like Thunderbird, Roundcube, etc.) submitting outbound mail to their provider. Unlike port 25, port 587 **requires** authentication and is expected to use STARTTLS for security. Thus, everyday users typically configure their outgoing (SMTP) settings to use port 587.
+
+- **Port 465**: Once used unofficially as "smtps" (SMTP over SSL/TLS), this port was deprecated but later reinstated by the IANA. Some providers offer it as a way for clients to connect using implicit SSL/TLS from the outset. While port 465 isn't as widely used as 587, it still offers direct, always-encrypted submission for some clients.
+
+## IMAP and its alternatives: reading your mail
+
+IMAP (internet message access protocol) allows mail clients to retrieve messages from a central server, maintaining synchronization across devices.
+
+- **Port 143**: The standard IMAP port. Connections here start unencrypted and, like SMTP, can be "upgraded" to encrypted status using STARTTLS. For historical and compatibility reasons, this port still sees significant use, though encryption is strongly encouraged.
+
+- **Port 993**: Secure IMAP (commonly called IMAPS) runs here. It uses implicit TLS, meaning the connection starts out encrypted. This is the go-to for secure email retrieval in most client software today.
+
+### Email client configuration
+
+A typical configuration for fetching your mail from the mailserver `mx.example.com` looks like:
+
+```
+Incoming IMAP server: mx.example.com
+Port: 993
+Security: SSL/TLS
+Username: you@example.com
+Password: your-super-secure-password
+```
+
+The config for sending emails:
+```
+Outgoing SMTP server: mx.example.com
+Port: 587
+Security: STARTTLS (or "require encryption")
+Username: you@example.com
+Password: your-super-secure-password
+```
+
+## JMAP: a modern approach
+
+[JMAP](https://jmap.io/) (JSON meta application protocol) is a greatly simplified protocol by Fastmail that has not yet seen widespread adoption. Despite it similifying APIs, overly complicated exchange/upgrade protocols, increasing flexibility, and requiring encryption from the start, it hasn't been adopted by the email giants like Gmail, Outlook, etc.
+
+JMAP isn’t tied to traditional email ports - it leverages HTTPS for communication, allows clients to manage messages, calendars, and contacts using JSON formatting. JMAP adoption would reduce bandwidth and simplify multi-device synchronization, especially over mobile networks.
+
+> Regardless, the open-source mailserver
Stalwart Mail supports JMAP out of the box. This is also the mailserver we recommend for self-hosters because of privacy and security reasons, as well as ease of use and flexibility.
+
+[It is speculated that JMAP will never see widespread adoption](https://news.ycombinator.com/item?id=42493172) and suffers from its flaws, but a modern email protocol that's not plagued by past bad design decisions is long overdue.
+
+Providers supporting JMAP typically direct you to a URL such as:
+
+```
+https://example.hexname.com/jmap
+```
+
+
+## Summary
+
+| Port | Protocol | Use Case | Encryption |
+|------|------------|---------------------------------|----------------------------|
+| 25 | SMTP | Server-to-server mail delivery | STARTTLS optional |
+| 587 | Submission | Client outgoing mail | STARTTLS required |
+| 465 | SSMTPS | Legacy/alternate encrypted SMTP | SSL/TLS required |
+| 143 | IMAP | Client mail retrieval | STARTTLS optional |
+| 993 | IMAPS | Secure mail retrieval | SSL/TLS required |
+| 443 | JMAP/HTTPS | Modern mail access (web API) | SSL required |
+
+
+If you need to set up DNS records for your mailserver without nonsense, and fast, you can use a service like
HexName to own your mail infrastructure.
diff --git a/src/lib/posts/why-ddns-is-essential-for-homelab-setups-with-public-ipv4.md b/src/lib/posts/why-ddns-is-essential-for-homelab-setups-with-public-ipv4.md
new file mode 100644
index 0000000..9207f83
--- /dev/null
+++ b/src/lib/posts/why-ddns-is-essential-for-homelab-setups-with-public-ipv4.md
@@ -0,0 +1,41 @@
+---
+title: "DDNS explained: Tutorial, usage, and importance for homelabs"
+subtitle: Understanding DDNS, CGNAT, and network accessibility for homelabbers
+description: Learn how DDNS helps homelab enthusiasts with external IPv4 addresses, why Carrier-Grade NAT blocks DDNS, and how to check your network setup and troubleshoot accessibility issues.
+---
+
+# Why Dynamic DNS is essential for homelab setups with a public IPv4
+
+Homelabbers running self-hosted services like game servers, file shares, or mail often face the challenge of connecting reliably from outside their home network. This is where DDNS (Dynamic Domain Name System, or DynDNS) becomes a key tool - especially for those with public IPv4 addresses. However, DDNS does not work the same for everyone, and Carrier-Grade NATs (CGNAT) often create limitations.
+
+## What is DDNS?
+
+DDNS allows you to automatically update DNS records with your dynamic external IPv4 address, so you can access your services easily using a domain name instead of memorizing IPs. If your home ISP gives you a non-static (dynamic) IP and you want to access `server.example.hexname.com`, DDNS providers keep this domain pointed to your current public IP.
+
+For example, by creating an A record for `home.example.hexname.com` at a service like
HexName, and by periodically running a simple script on your home network, anyone connecting to this hostname will reach your actual home server - even if your IP changes every day.
+
+## How CGNATs prevents DDNS from working
+
+Many ISPs now use Carrier-Grade NATs to conserve limited IPv4 space. Instead of assigning a unique public address to each customer, ISPs put many users behind a single external IP. Your router gets a local address (like `100.64.0.15`), and only the ISP’s shared gateway gets a publically routable IP address.
+
+Because of this extra layer, DDNS updates the DNS record to point to your ISP’s shared IP. Connections from the outside will never reach your router directly, since the ISP's router won't know which host is meant by the packet. This is why DDNS is ineffective behind CGNAT, and cannot open inbound connections for you, no matter the DNS configuration.
+
+## How to check if you have a public IPv4
+
+To confirm you’re not behind CGNAT:
+
+1. Log in to your router’s web interface. This is usually at `192.168.1.1` or `192.168.0.1`.
+2. Find the section labeled "Status," "Internet," or "WAN" (Wide Area Network).
+3. Look for your displayed "external IPv4 address".
+
+To verify, look up “What is my IP” online and compare it with the router’s external IPv4. If they match, you have a "real" publically routable IP and DDNS will work as expected.
+
+> Otherwise if the external IP in the router's interface is in the private range (e.g., `100.64.0.0/10`, `10.0.0.0/8`, `192.168.0.0/16`, or `172.16.0.0/12`), this also means that you're behind some sort of CGNAT.
+
+> Some ISPs offer public IPs as a paid feature, so it’s worth asking them if you'd benefit from DDNS.
+
+## Example DDNS usage in a homelab
+
+If you have a true public IPv4, register a subdomain like `example.hexname.com` on
HexName, and set up a DDNS script to keep your record updated. This makes it possible to access your homelab remotely, run services, or even share files with friends securely, without worrying about changing IPs, proxying, or complicated URL sharing.
+
+Homelabbing is the backbone of private cloud, self-hosted apps, and learning real-world networking—knowing your IP setup is the first step to an accessible, flexible lab.
diff --git a/src/lib/posts/why-vps-providers-block-outgoing-email-ports-by-default-due-to-spam.md b/src/lib/posts/why-vps-providers-block-outgoing-email-ports-by-default-due-to-spam.md
new file mode 100644
index 0000000..ce4b13d
--- /dev/null
+++ b/src/lib/posts/why-vps-providers-block-outgoing-email-ports-by-default-due-to-spam.md
@@ -0,0 +1,37 @@
+---
+title: Why VPS providers block outgoing email ports by default
+subtitle: Understanding default SMTP port restrictions on VPS hosting
+description: Many VPS providers block outgoing email ports to mitigate spam and prevent IP blacklisting. This article explains the technical reasons, real-world consequences, and industry best practices for managing email delivery on virtual servers.
+---
+
+# Why VPS providers block outgoing email ports by default due to spam
+
+Email remains a core method of internet communication. Its original technical design predates many modern safeguards, making it simple to send - but also easily abused for spam. This article covers why VPS (virtual private server) hosting companies commonly restrict outgoing ports related to email, like `25`, `465`, and `587`, and what users can do about it.
+
+## How email spam developed
+
+The Simple Mail Transfer Protocol (SMTP) forms the backbone of email and was designed decades ago with minimal barriers to sending messages. Because of this, automated tools can send massive volumes of unsolicited emails with little technical difficulty or computational cost.
+
+Historically, this resulted in abuse by senders distributing unwanted advertising, scams, and phishing attempts to every address they could find. This, in turn, led developers and administrators to invent anti-spam mechanisms to preserve the reliability and usability of email.
+
+Ironically, the [first-ever email spam](https://www.templetons.com/brad/spam/spam25.html) was sent by an MIT sysadmin of CTSS in 1971 to hundreds of ARPANET users warning about email spam that began with the sentence:
+> "There is no way to peace. Peace is the way."
+
+## Spam blocklists and mailserver reputation
+
+To fight junk mail, the industry relies on publicly available blocklists. If a mailserver's IP address is reported or detected as sending spam, it is added to these lists and may be denied by receiving servers. Some key features:
+
+- **Reputation systems**: Large email providers (Gmail, Outlook, iCloud Mail, Yahoo, etc.) maintain internal tracking of sender reputation, making delivery difficult for servers with histories of abuse.
+- **Blocklist checks**: Publically available spam blocklists maintain a list of IPs that send out unwanted emails in large amounts. You can use free online services to check if your server's IP is on these lists. They usually include options to appeal to the block.
+
+For example, after obtaining an IP address from your hosting provider, you can check your mailserver's IP reputation with the popular lists such as [Spamhaus](https://www.spamhaus.org/ip-reputation/) or [MXToolBox's free tool](https://mxtoolbox.com/blacklists.aspx) and appeal to the blocklists directly.
+
+## VPS providers and port restrictions
+
+Due to the ease of obtaining new IPs and cheap temrporary servers, spammers have historically used them to launch mass email campaigns. Nowadays, to limit abuse, most VPS providers block outgoing traffic on SMTP standard ports (such as `25`, `465`) by default.
+
+If your server needs to send legitimate email, contact your VPS provider to request port unblocking.
+
+You can also use an SMTP relay service, which handles hosting the mailserver for you. This isn't really a viable option though if you're looking to self-host your mailserver, and learn about the intricacies of email.
+
+For users needing to get a mailserver up and running simply and fast, free DNS hosting services like
HexName allow registration of subdomains (like `example.hexname.com`) and creation of necessary DNS entries such as MX records for mail handling, TXT for SPF/DKIM, SRV, and so on.
diff --git a/src/routes/+layout.svelte b/src/routes/+layout.svelte
index 16a97d7..06005ae 100644
--- a/src/routes/+layout.svelte
+++ b/src/routes/+layout.svelte
@@ -9,12 +9,15 @@
import { getSubdomains, getBaseDomains } from '$lib/domains.svelte';
import Footer from '$lib/Footer.svelte';
import { page } from '$app/state';
- import { afterNavigate } from '$app/navigation';
+ import { afterNavigate, goto } from '$app/navigation';
let { children } = $props();
onMount(async () => {
await initUserAuthStatus();
+ if (isDashboard && !auth.isAuthenticated) {
+ goto("/login");
+ }
getBaseDomains();
if (auth.isAuthenticated) {
diff --git a/src/routes/+page.svelte b/src/routes/+page.svelte
index 3a467f6..6c8c8bb 100644
--- a/src/routes/+page.svelte
+++ b/src/routes/+page.svelte
@@ -110,12 +110,12 @@