stroopwafel.amsterdam was registered on 19 Nov 2014 and is hosted on AS20857 Signet B.V. in Netherlands (Kingdom of the). We couldn't read an SSL certificate for it when we last analysed it.
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.
We couldn't read an SSL certificate on port 443 when we last analysed stroopwafel.amsterdam. Refresh the analysis to check again.
Is stroopwafel.amsterdam’s name taken on other extensions?
Every IP address stroopwafel.amsterdam resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| stroopwafel.amsterdam | 37.97.254.27 | 3600 |
| Host | IPv6 address | TTL |
|---|---|---|
| stroopwafel.amsterdam | 2a01:7c8:3:1337::27 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| stroopwafel.amsterdam | 10 stroopwafel.amsterdam | 3600 |
| Host | Name server | TTL |
|---|---|---|
| stroopwafel.amsterdam | ns0.transip.net | 21600 |
| stroopwafel.amsterdam | ns1.transip.nl | 21600 |
| stroopwafel.amsterdam | ns2.transip.eu | 21600 |
| Host | Text | TTL |
|---|---|---|
| stroopwafel.amsterdam | "v=spf1 ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| stroopwafel.amsterdam | ns0.transip.net hostmaster.transip.nl 2025043000 86400 1800 2419200 300 | 3600 |
| Host | Value | TTL |
|---|---|---|
| stroopwafel.amsterdam | 256 3 13 XW7wbLd6LwM8dX/OzFrpKAfBMhoLKEArN9hQetw/X6a6SKL8LEFXF/SyhU9BdBYRrp/q6fYGPejXFdTA7aJjrg== | 300 |
| stroopwafel.amsterdam | 257 3 13 V1sYmdlvsquF7L0bSDMbJuHMUtCsopPZrGm4vbFmPjiDFfdddj4aXz5tFMY0fUKA7aMuQJgw48cr/Q07BvxQZA== | 300 |
Other domains served from 37.97.254.27. Normal for shared hosting and CDNs.
No reviews yet. Used stroopwafel.amsterdam? 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.
stroopwafel.amsterdam has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
stroopwafel.amsterdam was registered on 19 Nov 2014, making it 11 years old. See Overview →
stroopwafel.amsterdam is served from 1 IP address, mainly on AS20857 Signet B.V. in Netherlands (Kingdom of the). See Hosting →
Raw registry data for stroopwafel.amsterdam. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.nic.amsterdam domain: AMSTERDAM organisation: Gemeente Amsterdam address: Amstel 1 address: Amsterdam 1011 PN address: Netherlands (the) contact: administrative name: Managing Director organisation: SIDN (Stichting Internet Domeinregistratie Nederland) address: P.O. Box 5022 address: Arnhem 6802 EA address: Netherlands (the) phone: +31 26 3525500 e-mail: [email protected] contact: technical name: Operational Director organisation: SIDN (Stichting Internet Domeinregistratie Nederland) address: P.O. Box 5022 address: Arnhem 6802 EA address: Netherlands (the) phone: +31 26 3525500 e-mail: [email protected] nserver: NS1.DNS.AMSTERDAM 194.0.28.4 2001:678:2c:0:194:0:28:4 nserver: NS3.DNS.AMSTERDAM 194.0.25.26 2001:678:20:0:0:0:0:26 nserver: NS4.DNS.AMSTERDAM 185.159.199.202 2620:10a:80ac:0:0:0:0:202 ds-rdata: 29930 13 2 66e790789a927fe0510dffbc2309654d9cc1b4d32fb3797b6ea6f31cad59d7f3 whois: whois.nic.amsterdam status: ACTIVE remarks: Registration information: http://www.nic.amsterdam created: 2014-11-20 changed: 2023-07-18 source: IANA
The first response from http://www.stroopwafel.amsterdam, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with stroopwafel.amsterdam. 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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.