debian.jp is registered with whois.jprs.jp. Its SSL certificate doesn't cover this domain name, so browsers warn visitors.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
3 of 6 recommended headers
Forces HTTPS on future visits.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
No robots.txt, so every crawler may crawl the whole site. Not every crawler follows it. llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
Is debian.jp’s name taken on other extensions?
| Host | IPv4 address | TTL |
|---|---|---|
| debian.jp | 160.16.98.142 | 86400 |
| Host | Name server | TTL |
|---|---|---|
| debian.jp | ns1.value-domain.com | 86400 |
| debian.jp | ns2.value-domain.com | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| debian.jp | ns1.value-domain.com hostmaster.debian.jp 2023061508 3600 900 604800 86400 | 86400 |
No reviews yet. Used debian.jp? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
debian.jp has no community safety rating yet. Its SSL certificate doesn't cover this domain name, so browsers warn visitors. See Security →
debian.jp is registered through whois.jprs.jp. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
Raw registry data for debian.jp. May be redacted by privacy services.
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: [ドメイン情報] [Domain Name] DEBIAN.JP [登録者名] Debian開発者の会 [Registrant] Debian JP Project [Name Server] ns1.value-domain.com [Name Server] ns2.value-domain.com [Name Server] ns3.value-domain.com [Name Server] ns4.value-domain.com [Name Server] ns5.value-domain.com [Signing Key] [登録年月日] 2001/05/01 [有効期限] 2027/05/31 [状態] Active [最終更新] 2026/09/18 14:04:38 (JST) Contact Information: [公開連絡窓口] [名前] Whois情報公開代行サービス by バリュードメイン [Name] Whois Privacy Protection Service by VALUE-DOMAIN [Email] [email protected] [Web Page] [郵便番号] 530-0011 [住所] 大阪府大阪市北区大深町3-1 グランフロント大阪 タワーB 23階 [Postal Address] [電話番号] 06-7634-2727 [電話番号] 06-6374-0121 [FAX番号]
The first response from http://www.debian.jp, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with debian.jp. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, https://www.debian.or.jp/
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 24 Oct 2026.