domain/svettigarummet.lol
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archivesvettigarummet.lol was registered in August 2026 with NameSilo, and is due to expire in August 2027. Its website was online at the last check, served from Amazon.com's network. svettigarummet.lol doesn't receive email: it publishes no mail servers. The website presents it as Rift Recap (discord custom league).
Based on what we observed, it was registered within the last year and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 216.198.79.1 AS16509 · Amazon.com, Inc. · US |
| A | 64.29.17.1 AS16509 · Amazon.com, Inc. · US |
| NS | ns1.olitt.com |
| SOA | ns8.cloudoon.com hostmaster.cloudoon.com 2026090105 |
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 1 page, some only in part.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. svettigarummet.lol is registered through NameSilo. The website presents itself as Rift Recap; that is the site's own claim, not a verified owner.
svettigarummet.lol was registered on 31 Aug 2026, making it 2 months old.
The registry lists 31 Aug 2027 as the expiry date, 284 days from now. Most domains renew automatically before then.
svettigarummet.lol's website is served from Amazon.com's network.
No one: svettigarummet.lol publishes no MX records, so it can't receive email.
It was up when we last checked, 3 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.