otakurepublic.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 138 days left15 years oldTranco #192455
80
otakurepublic.com was registered on 1 Apr 2011 via GMO Internet Group, Inc. d/b/a Onamae.com and the registry expiry is 1 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
otakurepublic.com publishes 4 nameservers. DNSSEC is not signed.
otakurepublic.com has 1 IPv4 address (54.214.233.0). The geolocation database places 54.214.233.0 in Boardman, United States.
The TLS certificate from RapidSSL TLS ECC CA G1 is valid and has 138 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Google Analytics, HSTS, Nginx, Pinterest, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for otakurepublic.com in the checks that ran.
Domain · RDAP/WHOIS
otakurepublic.com was registered on 1 Apr 2011 via GMO Internet Group, Inc. d/b/a Onamae.com. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
| Registered | since 1 Apr 2011 |
|---|---|
| Created | 1 April 2011 |
| Updated | 16 March 2026 |
| Expires | 1 April 2027 |
| Registrar | GMO Internet Group, Inc. d/b/a Onamae.com |
| Status | active |
| Nameservers | 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/otakurepublic.com |
Nameserver 01.dnsv.jp is published for otakurepublic.com in the registration record from https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
Nameserver 02.dnsv.jp is published for otakurepublic.com in the registration record from https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
Nameserver 03.dnsv.jp is published for otakurepublic.com in the registration record from https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
Nameserver 04.dnsv.jp is published for otakurepublic.com in the registration record from https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
DNS
otakurepublic.com has 1 address record, 7 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 54.214.233.0 |
|---|---|
| AAAA | — |
| NS | 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (20) Google, aspmx2.googlemail.com (30) Google, aspmx3.googlemail.com (30) Google, aspmx4.googlemail.com (30) Google, aspmx5.googlemail.com (30) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at otakurepublic.com is "v=spf1 ip4:54.214.233.0 include:spf.haihaimail.jp include:_spf.google.com include:spf.bmv.jp ~all".
The DMARC text record at _dmarc.otakurepublic.com is "v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]".
IPv4 address 54.214.233.0 answers for otakurepublic.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx4.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx5.googlemail.com has preference 30. The host is recognised as Google.
Hosting and geo
otakurepublic.com is placed in Boardman, United States by the local geolocation database (db-ip).
| Address | 54.214.233.0 |
|---|---|
| Country | United States |
| City | Boardman |
| Source | db-ip |
SSL/TLS
The certificate for otakurepublic.com is valid, with 138 days left and 2 subject alternative names. Source: tls:443.
| Issuer | RapidSSL TLS ECC CA G1 |
|---|---|
| Subject | otakurepublic.com |
| Valid from | 1 September 2026 |
| Valid until | 18 March 2027 |
| Days left | 138 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: otakurepublic.com, www.otakurepublic.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Google Analytics · Analytics
- HSTS · Security
- Nginx · Web servers, Reverse proxies
- Pinterest · Widgets
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Google Analytics is filed under Analytics.
HSTS is filed under Security.
Nginx is filed under Web servers, Reverse proxies.
Pinterest is filed under Widgets.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 512 ms. The target title is 70 characters and the page has 3 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 512 ms |
| Title length | 70 no |
| Quoted title | "Otaku Republic - The largest Yaoi (bl / slash) Doujinshi online store." |
| Meta description | "Otaku Republic is the largest Doujinshi online shop. Over 2,000,000 Doujinshi and Doujin items." yes |
| H1 count | 3 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://otakurepublic.com/ |
| Language | en |
| Links | 250 |
| Images | 29 |
| Favicon | yes |
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 otakurepublic.com 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 | yes |
| 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 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 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 Boardman.
- October 2026: geo country changed from empty to United States.
Questions
Is otakurepublic.com 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 otakurepublic.com?
otakurepublic.com is placed in Boardman, United States.
When does otakurepublic.com expire?
otakurepublic.com expires on 1 April 2027 according to https://rdap.verisign.com/com/v1/domain/otakurepublic.com.
Who owns otakurepublic.com?
The registry did not return a person or a company for otakurepublic.com. RDAP often redacts the registrant. The registrar on file is GMO Internet Group, Inc. d/b/a Onamae.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/otakurepublic.com at 2026-10-30T14:08:27Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:08:27Z
- TLS source tls:443 at 2026-10-30T14:08:27Z
- HTTP source https://otakurepublic.com/ at 2026-10-30T14:08:27Z
- Tech source wappalyzergo at 2026-10-30T14:08:27Z
- Geo source db-ip at 2026-10-30T14:08:27Z
- Safety source family DNS and local lists at 2026-10-30T14:08:27Z
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.