mindawinci.no

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

HTTP 403SafeSSL: 130 days left5 years old

One re-check per domain each UTC day.

50

mindawinci.no was registered on 17 Sep 2021 via GoDaddy.com LLC. WHOIS data came from RDAP at https://rdap.norid.no/domain/mindawinci.no.

mindawinci.no publishes 4 nameservers. DNSSEC is not signed.

mindawinci.no has 2 IPv4 addresses (13.248.128.131, 76.223.0.150). The geolocation database places 13.248.128.131 in Montreal, Canada.

The TLS certificate from Amazon RSA 2048 M04 is valid and has 130 days left (TLS 1.2).

Tech detection named Amazon ELB and Amazon Web Services. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for mindawinci.no in the checks that ran.

Domain · RDAP/WHOIS

mindawinci.no was registered on 17 Sep 2021 via GoDaddy.com LLC. The registry returned 0 status values and 4 nameservers from https://rdap.norid.no/domain/mindawinci.no.

Registeredsince 17 Sep 2021
Created17 September 2021
Updated29 August 2026
Expires—
RegistrarGoDaddy.com LLC
Status—
Nameserversns-94.awsdns-11.com, ns-1088.awsdns-08.org, ns-1670.awsdns-16.co.uk, ns-535.awsdns-02.net
DNSSECno
Sourcehttps://rdap.norid.no/domain/mindawinci.no

Nameserver ns-94.awsdns-11.com is published for mindawinci.no in the registration record from https://rdap.norid.no/domain/mindawinci.no.

Nameserver ns-1088.awsdns-08.org is published for mindawinci.no in the registration record from https://rdap.norid.no/domain/mindawinci.no.

Nameserver ns-1670.awsdns-16.co.uk is published for mindawinci.no in the registration record from https://rdap.norid.no/domain/mindawinci.no.

Nameserver ns-535.awsdns-02.net is published for mindawinci.no in the registration record from https://rdap.norid.no/domain/mindawinci.no.

DNS

mindawinci.no has 2 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.

A13.248.128.131, 76.223.0.150
AAAA—
NSns-1088.awsdns-08.org, ns-1670.awsdns-16.co.uk, ns-535.awsdns-02.net, ns-94.awsdns-11.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 13.248.128.131 answers for mindawinci.no at resolver 1.1.1.1:53.

IPv4 address 76.223.0.150 answers for mindawinci.no at resolver 1.1.1.1:53.

Hosting and geo

mindawinci.no is placed in Montreal, Canada by the local geolocation database (db-ip).

Address13.248.128.131
CountryCanada
CityMontreal
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for mindawinci.no is valid, with 130 days left and 2 subject alternative names. Source: tls:443.

IssuerAmazon RSA 2048 M04
Subject*.mindawinci.no
Valid from9 February 2026
Valid until10 March 2027
Days left130
SAN count2
ProtocolTLS 1.2
Sourcetls:443

Subject alternative names: *.mindawinci.no, mindawinci.no.

Tech stack

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

  • Amazon ELB · Load balancers
  • Amazon Web Services · PaaS

Amazon ELB is filed under Load balancers.

Amazon Web Services is filed under PaaS.

On-page checks

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

Status403
TTFB24 ms
Title length13 yes
Quoted title"403 Forbidden"
Meta descriptionnone no
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links0
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 mindawinci.no is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

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 10 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

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

Safety lists 15 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: geo city changed from empty to Montreal.
  • October 2026: geo country changed from empty to Canada.

Questions

Is mindawinci.no safe?

The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.

Who hosts mindawinci.no?

mindawinci.no is placed in Montreal, Canada.

When does mindawinci.no expire?

No expiry date was returned for mindawinci.no.

Who owns mindawinci.no?

The registry did not return a person or a company for mindawinci.no. RDAP often redacts the registrant. The registrar on file is GoDaddy.com LLC.

Sources

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

Methodology

Related reports

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

.no GoDaddy.com LLC

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.