snickare-laholm.se was registered with Loopia AB on 9 Jun 2024 and is hosted on AS16509 Amazon.com Inc. in United States of America. Its SSL certificate from Google Trust Services expired on 5 Nov 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is snickare-laholm.se’s name taken on other extensions?
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address snickare-laholm.se resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| snickare-laholm.se | 3.168.73.123 | 31 |
| snickare-laholm.se | 3.168.73.124 | 31 |
| snickare-laholm.se | 3.168.73.19 | 31 |
| snickare-laholm.se | 3.168.73.84 | 31 |
| Host | Mail server | TTL |
|---|---|---|
| snickare-laholm.se | 10 mx1.improvmx.com | 300 |
| snickare-laholm.se | 20 mx2.improvmx.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| snickare-laholm.se | ns-1254.awsdns-28.org | 21600 |
| snickare-laholm.se | ns-128.awsdns-16.com | 21600 |
| snickare-laholm.se | ns-2045.awsdns-63.co.uk | 21600 |
| snickare-laholm.se | ns-708.awsdns-24.net | 21600 |
| Host | Text | TTL |
|---|---|---|
| snickare-laholm.se | "v=spf1 include:spf.improvmx.com ~all" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| snickare-laholm.se | ns-1254.awsdns-28.org awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 3.168.73.19. Normal for shared hosting and CDNs.
No reviews yet. Used snickare-laholm.se? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
snickare-laholm.se has no community safety rating yet. Its SSL certificate expired on 5 Nov 2024. See Security →
snickare-laholm.se is registered through Loopia AB. See WHOIS →
The registration expired on 9 Jun 2025. See Overview →
snickare-laholm.se was registered on 9 Jun 2024, making it 2 years old. See Overview →
snickare-laholm.se is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
We detected 1 technology, including Google Analytics. See Built with →
Raw registry data for snickare-laholm.se. May be redacted by privacy services.
# Copyright (c) 1997- The Swedish Internet Foundation. # All rights reserved. # The information obtained through searches, or otherwise, is protected # by the Swedish Copyright Act (1960:729) and international conventions. # It is also subject to database protection according to the Swedish # Copyright Act. # Any use of this material to target advertising or # similar activities is forbidden and will be prosecuted. # If any of the information below is transferred to a third # party, it must be done in its entirety. This server must # not be used as a backend for a search engine. # Result of search for registered domain names under # the .se top level domain. # This whois printout is printed with UTF-8 encoding. # state: active domain: snickare-laholm.se holder: lai3617-3290366 created: 2024-06-10 modified: 2024-06-10 expires: 2025-06-10 nserver: ns-708.awsdns-24.net nserver: ns-2045.awsdns-63.co.uk 205.251.199.253 nserver: ns-128.awsdns-16.com nserver: ns-1254.awsdns-28.org 205.251.196.230 dnssec: unsigned delegation registry-lock: unlocked status: ok registrar: Loopia AB
The first response from http://www.snickare-laholm.se, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with snickare-laholm.se. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.