intimcity.nl

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 87 days left16 years old

One re-check per domain each UTC day.

65

intimcity.nl was registered on 11 Jun 2010 via NAMECHEAP, INC.. WHOIS data came from RDAP at https://rdap.sidn.nl/domain/intimcity.nl.

intimcity.nl publishes 2 nameservers. DNSSEC is not signed.

intimcity.nl has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 87 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

intimcity.nl was registered on 11 Jun 2010 via NAMECHEAP, INC.. The registry returned 1 status value and 2 nameservers from https://rdap.sidn.nl/domain/intimcity.nl.

Registeredsince 11 Jun 2010
Created11 June 2010
Updated15 December 2022
Expires—
RegistrarNAMECHEAP, INC.
Statusactive
Nameserverskehlani.ns.cloudflare.com, zod.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.sidn.nl/domain/intimcity.nl

Nameserver kehlani.ns.cloudflare.com is published for intimcity.nl in the registration record from https://rdap.sidn.nl/domain/intimcity.nl.

Nameserver zod.ns.cloudflare.com is published for intimcity.nl in the registration record from https://rdap.sidn.nl/domain/intimcity.nl.

DNS

intimcity.nl has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A188.114.96.4, 188.114.97.4
AAAA2a06:98c1:3120::3, 2a06:98c1:3121::3
NSkehlani.ns.cloudflare.com, zod.ns.cloudflare.com
MXmx1-hosting.jellyfish.systems (5), mx2-hosting.jellyfish.systems (10), mx3-hosting.jellyfish.systems (20)
SPFpresent
DMARCpresent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at intimcity.nl is "v=spf1 +a +a:server706.web-hosting.com +mx +ip4:198.177.120.188 +ip4:198.177.120.192 include:spf.web-hosting.com ~all".

The DMARC text record at _dmarc.intimcity.nl is "v=DMARC1; p=none;".

IPv4 address 188.114.96.4 answers for intimcity.nl at resolver 1.1.1.1:53.

IPv4 address 188.114.97.4 answers for intimcity.nl at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3120::3 answers for intimcity.nl at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3121::3 answers for intimcity.nl at resolver 1.1.1.1:53.

Mail exchanger mx1-hosting.jellyfish.systems has preference 5.

Mail exchanger mx2-hosting.jellyfish.systems has preference 10.

Mail exchanger mx3-hosting.jellyfish.systems has preference 20.

Hosting and geo

intimcity.nl is placed in Toronto, Canada by the local geolocation database (db-ip).

Address188.114.96.4
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for intimcity.nl is valid, with 87 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectintimcity.nl
Valid from28 October 2026
Valid until26 January 2027
Days left87
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.intimcity.nl, intimcity.nl.

Tech stack

Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • HSTS · Security
  • HTTP/3 · Miscellaneous

Cloudflare is filed under CDN.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

On-page checks

The homepage returned HTTP 200 in 24 ms. The target title is 16 characters and the page has 1 H1 heading.

Status200
TTFB24 ms
Title length16 yes
Quoted title"��������� ������"
Meta descriptionnone no
H1 count1
HSTSyes yes
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links3
Images0
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for intimcity.nl is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

Cloudflare family DNS returned a block for intimcity.nl. That resolver covers adult and malware names.

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 5 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
  • October 2026: dns aaaa changed from 2a06:98c1:3120::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.

Questions

Is intimcity.nl safe?

Cloudflare family DNS returned a block for intimcity.nl. That resolver covers adult and malware names.

Who hosts intimcity.nl?

intimcity.nl is placed in Toronto, Canada.

When does intimcity.nl expire?

No expiry date was returned for intimcity.nl.

Who owns intimcity.nl?

The registry did not return a person or a company for intimcity.nl. RDAP often redacts the registrant. The registrar on file is NAMECHEAP, INC..

Sources

  • RDAP source https://rdap.sidn.nl/domain/intimcity.nl at 2026-10-30T14:59:20Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:59:20Z
  • TLS source tls:443 at 2026-10-30T14:59:20Z
  • HTTP source https://intimcity.nl/ at 2026-10-30T14:59:20Z
  • Tech source wappalyzergo at 2026-10-30T14:59:20Z
  • Geo source db-ip at 2026-10-30T14:59:20Z
  • Safety source family DNS and local lists at 2026-10-30T14:59:20Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.nl NAMECHEAP, INC.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.