komicolle.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
komicolle.org was registered on 16 Apr 2014 via Squarespace Domains II LLC and the registry expiry is 16 Apr 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
komicolle.org publishes 4 nameservers. DNSSEC is not signed.
komicolle.org has 1 IPv4 address (160.16.211.116). The geolocation database places 160.16.211.116 in Osaka, Japan.
No safety warning was recorded for komicolle.org in the checks that ran.
komicolle.org was registered on 16 Apr 2014 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
| Registered | since 16 Apr 2014 |
|---|---|
| Created | 16 April 2014 |
| Updated | 12 August 2026 |
| Expires | 16 April 2027 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns-cloud-b1.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org |
komicolle.org carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
komicolle.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 ns-cloud-b1.googledomains.com is published for komicolle.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
Nameserver ns-cloud-b4.googledomains.com is published for komicolle.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
Nameserver ns-cloud-b2.googledomains.com is published for komicolle.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
Nameserver ns-cloud-b3.googledomains.com is published for komicolle.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
komicolle.org has 1 address record, 7 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 160.16.211.116 |
|---|---|
| AAAA | — |
| NS | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com |
| MX | gmr-smtp-in.l.google.com (5) Google, alt1.gmr-smtp-in.l.google.com (10) Google, mxa.mailgun.org (10), mxb.mailgun.org (10), alt2.gmr-smtp-in.l.google.com (20) Google, alt3.gmr-smtp-in.l.google.com (30) Google, alt4.gmr-smtp-in.l.google.com (40) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at komicolle.org is "v=spf1 include:mailgun.org ~all".
IPv4 address 160.16.211.116 answers for komicolle.org at resolver 1.1.1.1:53.
Mail exchanger gmr-smtp-in.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt1.gmr-smtp-in.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger mxa.mailgun.org has preference 10.
Mail exchanger mxb.mailgun.org has preference 10.
Mail exchanger alt2.gmr-smtp-in.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt3.gmr-smtp-in.l.google.com has preference 30. The host is recognised as Google.
Mail exchanger alt4.gmr-smtp-in.l.google.com has preference 40. The host is recognised as Google.
komicolle.org is placed in Osaka, Japan by the local geolocation database (db-ip).
| Address | 160.16.211.116 |
|---|---|
| Country | Japan |
| City | Osaka |
| Source | db-ip |
No TLS certificate was read for komicolle.org on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 160.16.211.116:443: connect: connection refused
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://komicolle.org/": dial tcp 160.16.211.116:443: connect: connection refused
Family DNS for komicolle.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.
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
komicolle.org is placed in Osaka, Japan.
komicolle.org expires on 16 April 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/komicolle.org.
The registry did not return a person or a company for komicolle.org. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.