scilinks.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 68 days left28 years old
55
scilinks.org was registered on 17 Nov 1997 via NameCheap, Inc. and the registry expiry is 16 Nov 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org.
scilinks.org publishes 2 nameservers. DNSSEC is not signed.
scilinks.org 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 68 days left (TLS 1.3).
No safety warning was recorded for scilinks.org in the checks that ran.
Domain · RDAP/WHOIS
scilinks.org was registered on 17 Nov 1997 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org.
| Registered | since 17 Nov 1997 |
|---|---|
| Created | 17 November 1997 |
| Updated | 22 October 2026 |
| Expires | 16 November 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | jule.ns.cloudflare.com, rocky.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org |
scilinks.org carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver jule.ns.cloudflare.com is published for scilinks.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org.
Nameserver rocky.ns.cloudflare.com is published for scilinks.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org.
DNS
scilinks.org has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | jule.ns.cloudflare.com, rocky.ns.cloudflare.com |
| MX | scilinks-org.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at scilinks.org is "v=spf1 include:spf.protection.outlook.com ~all".
IPv4 address 188.114.96.4 answers for scilinks.org at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for scilinks.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for scilinks.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for scilinks.org at resolver 1.1.1.1:53.
Mail exchanger scilinks-org.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
A random label under scilinks.org also resolved, which means wildcard DNS is on.
Hosting and geo
scilinks.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for scilinks.org is valid, with 68 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | scilinks.org |
| Valid from | 9 October 2026 |
| Valid until | 8 January 2027 |
| Days left | 68 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.scilinks.org, scilinks.org.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for scilinks.org is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is scilinks.org 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 scilinks.org?
scilinks.org is placed in Toronto, Canada.
When does scilinks.org expire?
scilinks.org expires on 16 November 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org.
Who owns scilinks.org?
The registry did not return a person or a company for scilinks.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/scilinks.org at 2026-10-30T15:03:33Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:03:33Z
- TLS source tls:443 at 2026-10-30T15:03:33Z
- HTTP source https://scilinks.org/ at 2026-10-30T15:03:33Z
- Tech source not available at 2026-10-30T15:03:33Z
- Geo source db-ip at 2026-10-30T15:03:33Z
- Safety source family DNS and local lists at 2026-10-30T15:03:33Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.