.hatenadiary.jp

Download .hatenadiary.jp domains

585 active domains

Public suffix · Under .jp · Operated by Japan Registry Services Co., Ltd. (JPRS)

TLD suffix +0.01% YoY Latest export · 0 days ago
🔒 Get the list
From €29 / month

About .hatenadiary.jp

.hatenadiary.jp is a multi-level public suffix sitting one level below .jp. Suffixes like this exist because registries reserve a second level for specific registrant categories. Registrants treat them as if they were top-level TLDs, and so do webatla datasets.

At a glance

Suffix.hatenadiary.jp
Parent TLD.jp
RegistryJapan Registry Services Co., Ltd. (JPRS)
Domains585
Growth (YoY)+0.01%
New domain registrations
17 last week
25 last month
Active domains
585
registered in this zone
Active websites
585
resolved successfully in the last export
DNS
585
domains with DNS records
Countries
1
countries represented (by hosting IP)
RDAP & WHOIS
241
domains with RDAP & WHOIS records

Database preview of .hatenadiary.jp domains

5 sample rows from the live database. Switch the dataset to see what each one contains, then preview the file or buy the full dataset.

webatla-hatenadiary-jp-all-2026-06-13.jsonl.zst · 585 rows · 4.3 KB · 23 columns Daily fresh export
DomainTLD suffixTLDDomain type
0-8.hatenadiary.jphatenadiary.jpjpPRIVATE
935.hatenadiary.jphatenadiary.jpjpPRIVATE
a2020-01.hatenadiary.jphatenadiary.jpjpPRIVATE
acata.hatenadiary.jphatenadiary.jpjpPRIVATE
akagenoakisan.hatenadiary.jphatenadiary.jpjpPRIVATE
DomainTLD suffixTLDDomain typeCountry by IPPR valueHarmonic valueDomain creation dateDomain expiration date
0-8.hatenadiary.jphatenadiary.jpjpPRIVATEUS00
935.hatenadiary.jphatenadiary.jpjpPRIVATEUS00
a2020-01.hatenadiary.jphatenadiary.jpjpPRIVATEUS00
acata.hatenadiary.jphatenadiary.jpjpPRIVATEUS00
akagenoakisan.hatenadiary.jphatenadiary.jpjpPRIVATEUS00
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesPR valueHarmonic valueDomain creation dateDomain expiration date
0-8.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 20018.245.175.53US{"x-twitter":["https://t.co/N80TMXNfoD","https://twitter.com/hamakn/status/1481533664991531009"]}2026-04-19AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx00
935.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 2003.173.161.114US{"x-twitter":["https://twitter.com/935/statuses/414008159875788800","https://twitter.com/935/statuses/408798406832685056","https://twitter.com/935/statuses/407338786524102657"]}2026-04-23AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx00
a2020-01.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 20018.245.46.117US{"youtube":["https://youtube.com/@masudatherapy?feature=shared"]}2026-04-23AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx00
acata.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 20018.245.46.117US{"github":["https://github.com/puremourning/vimspector","https://github.com/madzak/python-json-logger","https://github.com/googleapis/python-container/issues/6"]}2026-04-23AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx00
akagenoakisan.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 40418.245.46.117US{"facebook":["https://facebook.com/hatenablog"],"x-twitter":["https://twitter.com/hatenablog"]}2026-04-24HSTS, Nginx, jQuery, Twitter, Varnish, Open Graph, Hatena Blog, Twitter Ads, Facebook Pixel, Google Analytics00
DomainTLD suffixTLDDomain typeDNS last data checkedDNS StatusDNS records
0-8.hatenadiary.jphatenadiary.jpjpPRIVATE2026-06-05TRUE{"A":["18.245.175.53","18.245.175.6","18.245.175.61","18.245.175.93"]}
935.hatenadiary.jphatenadiary.jpjpPRIVATE2026-05-30TRUE{"A":["3.173.161.114","3.173.161.37","3.173.161.76","3.173.161.99"]}
a2020-01.hatenadiary.jphatenadiary.jpjpPRIVATE2026-05-30TRUE{"A":["18.245.46.117","18.245.46.2","18.245.46.4","18.245.46.6"]}
acata.hatenadiary.jphatenadiary.jpjpPRIVATE2026-06-05TRUE{"A":["18.245.46.117","18.245.46.2","18.245.46.4","18.245.46.6"]}
akagenoakisan.hatenadiary.jphatenadiary.jpjpPRIVATE2026-05-28TRUE{"A":["18.245.46.117","18.245.46.2","18.245.46.4","18.245.46.6"]}
DomainRDAP/WHOIS last data checkedRDAP/WHOIS methodDomain creation dateDomain expiration dateDomain last changedRegistrarRDAP/WHOIS RecordResponse Status RDAP/WHOIS
0-8.hatenadiary.jp2026-03-20WHOIS{"raw_response":"\r\nCannot process your search request.\r\n\r\nService currently unavailable due to incoming of a large amount of\r\nrequests.\r\n\r\nTry again later.\r\n\r\nFor details, see: https://jprs.jp/about/dom-search/whois/\r\n\r\n[ JPRS WHOIS LEGAL DISCLAIMER: ]\r\n[ ]\r\n[ The WHOIS service (the \"Service\") offered by Japan Registry Services Co., ]\r\n[ Ltd. (JPRS) and the access to the records in the JPRS WHOIS database (the ]\r\n[ \"Database\") are provided for information purposes and query-based public ]\r\n[ access. ]\r\n[ ]\r\n[ Neither JPRS nor any of its officers, directors, employees or agents ]\r\n[ makes any warranty as to the results to be obtained from use of the ]\r\n[ Service. JPRS specifically disclaims all warranties of any kind, ]\r\n[ whether express, implied or statutory, including, but not limited to, ]\r\n[ any warranties of title, non-infringement, merchantability or fitness ]\r\n[ for a particular purpose. ]\r\n[ In no event shall JPRS nor anyone else involved in creating, supporting, ]\r\n[ producing or delivering the Service be liable to you for any lost ]\r\n[ profits or costs, even if JPRS or such person has been advised of the ]\r\n[ possibility of such damages. ]\r\n[ ]\r\n[ JPRS allows you to use the Service only for lawful purposes and that, ]\r\n[ under no circumstances shall you use the Service to: (a) allow, enable ]\r\n[ or otherwise support the transmission by e-mail, telephone, postal mail, ]\r\n[ facsimile or other means of mass unsolicited, commercial advertising or ]\r\n[ solicitations to entities other than the data recipient's own existing ]\r\n[ customers; or (b) enable high volume, automated, electronic processes ]\r\n[ that send queries or data to the systems of any registry operator or ]\r\n[ ICANN-accredited registrar, except as reasonably necessary to register ]\r\n[ domain names or modify existing registrations. ]\r\n[ ]\r\n[ By submitting the query you agree to abide by these terms and further ]\r\n[ agree that JPRS may take measures to limit the use of the Service in ]\r\n[ order to protect the privacy of its registrants or the integrity of ]\r\n[ the Database. ]\r\n[ ]\r\n[ JPRS reserves the right to modify or change these terms at any time ]\r\n[ without prior or subsequent notification of any kind. ]\r\n[ ]\r\n[ For further information, use 'whois -h whois.jprs.jp help'. ]\r\n[ To express Japanese output, add '/j' at the end of command, ]\r\n[ e.g. 'whois -h whois.jprs.jp xxx/j'. ]\r\n[ ]\r\n[ For more information on Whois status codes, please visit ]\r\n[ https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en. ]\r\n"}Domain is active
935.hatenadiary.jp
a2020-01.hatenadiary.jp
acata.hatenadiary.jp
akagenoakisan.hatenadiary.jp2026-03-18WHOIS{"raw_response":"\r\nCannot process your search request.\r\n\r\nService currently unavailable due to incoming of a large amount of\r\nrequests.\r\n\r\nTry again later.\r\n\r\nFor details, see: https://jprs.jp/about/dom-search/whois/\r\n\r\n[ JPRS WHOIS LEGAL DISCLAIMER: ]\r\n[ ]\r\n[ The WHOIS service (the \"Service\") offered by Japan Registry Services Co., ]\r\n[ Ltd. (JPRS) and the access to the records in the JPRS WHOIS database (the ]\r\n[ \"Database\") are provided for information purposes and query-based public ]\r\n[ access. ]\r\n[ ]\r\n[ Neither JPRS nor any of its officers, directors, employees or agents ]\r\n[ makes any warranty as to the results to be obtained from use of the ]\r\n[ Service. JPRS specifically disclaims all warranties of any kind, ]\r\n[ whether express, implied or statutory, including, but not limited to, ]\r\n[ any warranties of title, non-infringement, merchantability or fitness ]\r\n[ for a particular purpose. ]\r\n[ In no event shall JPRS nor anyone else involved in creating, supporting, ]\r\n[ producing or delivering the Service be liable to you for any lost ]\r\n[ profits or costs, even if JPRS or such person has been advised of the ]\r\n[ possibility of such damages. ]\r\n[ ]\r\n[ JPRS allows you to use the Service only for lawful purposes and that, ]\r\n[ under no circumstances shall you use the Service to: (a) allow, enable ]\r\n[ or otherwise support the transmission by e-mail, telephone, postal mail, ]\r\n[ facsimile or other means of mass unsolicited, commercial advertising or ]\r\n[ solicitations to entities other than the data recipient's own existing ]\r\n[ customers; or (b) enable high volume, automated, electronic processes ]\r\n[ that send queries or data to the systems of any registry operator or ]\r\n[ ICANN-accredited registrar, except as reasonably necessary to register ]\r\n[ domain names or modify existing registrations. ]\r\n[ ]\r\n[ By submitting the query you agree to abide by these terms and further ]\r\n[ agree that JPRS may take measures to limit the use of the Service in ]\r\n[ order to protect the privacy of its registrants or the integrity of ]\r\n[ the Database. ]\r\n[ ]\r\n[ JPRS reserves the right to modify or change these terms at any time ]\r\n[ without prior or subsequent notification of any kind. ]\r\n[ ]\r\n[ For further information, use 'whois -h whois.jprs.jp help'. ]\r\n[ To express Japanese output, add '/j' at the end of command, ]\r\n[ e.g. 'whois -h whois.jprs.jp xxx/j'. ]\r\n[ ]\r\n[ For more information on Whois status codes, please visit ]\r\n[ https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en. ]\r\n"}Domain is active
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesDNS last data checkedDNS StatusDNS recordsPR valueHarmonic valueRDAP/WHOIS last data checkedRDAP/WHOIS methodDomain creation dateDomain expiration dateDomain last changedRegistrarRDAP/WHOIS RecordResponse Status RDAP/WHOIS
0-8.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 20018.245.175.53US{"x-twitter":["https://t.co/N80TMXNfoD","https://twitter.com/hamakn/status/1481533664991531009"]}2026-04-19AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx2026-06-05TRUE{"A":["18.245.175.53","18.245.175.6","18.245.175.61","18.245.175.93"]}002026-03-20WHOIS{"raw_response":"\r\nCannot process your search request.\r\n\r\nService currently unavailable due to incoming of a large amount of\r\nrequests.\r\n\r\nTry again later.\r\n\r\nFor details, see: https://jprs.jp/about/dom-search/whois/\r\n\r\n[ JPRS WHOIS LEGAL DISCLAIMER: ]\r\n[ ]\r\n[ The WHOIS service (the \"Service\") offered by Japan Registry Services Co., ]\r\n[ Ltd. (JPRS) and the access to the records in the JPRS WHOIS database (the ]\r\n[ \"Database\") are provided for information purposes and query-based public ]\r\n[ access. ]\r\n[ ]\r\n[ Neither JPRS nor any of its officers, directors, employees or agents ]\r\n[ makes any warranty as to the results to be obtained from use of the ]\r\n[ Service. JPRS specifically disclaims all warranties of any kind, ]\r\n[ whether express, implied or statutory, including, but not limited to, ]\r\n[ any warranties of title, non-infringement, merchantability or fitness ]\r\n[ for a particular purpose. ]\r\n[ In no event shall JPRS nor anyone else involved in creating, supporting, ]\r\n[ producing or delivering the Service be liable to you for any lost ]\r\n[ profits or costs, even if JPRS or such person has been advised of the ]\r\n[ possibility of such damages. ]\r\n[ ]\r\n[ JPRS allows you to use the Service only for lawful purposes and that, ]\r\n[ under no circumstances shall you use the Service to: (a) allow, enable ]\r\n[ or otherwise support the transmission by e-mail, telephone, postal mail, ]\r\n[ facsimile or other means of mass unsolicited, commercial advertising or ]\r\n[ solicitations to entities other than the data recipient's own existing ]\r\n[ customers; or (b) enable high volume, automated, electronic processes ]\r\n[ that send queries or data to the systems of any registry operator or ]\r\n[ ICANN-accredited registrar, except as reasonably necessary to register ]\r\n[ domain names or modify existing registrations. ]\r\n[ ]\r\n[ By submitting the query you agree to abide by these terms and further ]\r\n[ agree that JPRS may take measures to limit the use of the Service in ]\r\n[ order to protect the privacy of its registrants or the integrity of ]\r\n[ the Database. ]\r\n[ ]\r\n[ JPRS reserves the right to modify or change these terms at any time ]\r\n[ without prior or subsequent notification of any kind. ]\r\n[ ]\r\n[ For further information, use 'whois -h whois.jprs.jp help'. ]\r\n[ To express Japanese output, add '/j' at the end of command, ]\r\n[ e.g. 'whois -h whois.jprs.jp xxx/j'. ]\r\n[ ]\r\n[ For more information on Whois status codes, please visit ]\r\n[ https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en. ]\r\n"}Domain is active
935.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 2003.173.161.114US{"x-twitter":["https://twitter.com/935/statuses/414008159875788800","https://twitter.com/935/statuses/408798406832685056","https://twitter.com/935/statuses/407338786524102657"]}2026-04-23AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx2026-05-30TRUE{"A":["3.173.161.114","3.173.161.37","3.173.161.76","3.173.161.99"]}00
a2020-01.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 20018.245.46.117US{"youtube":["https://youtube.com/@masudatherapy?feature=shared"]}2026-04-23AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx2026-05-30TRUE{"A":["18.245.46.117","18.245.46.2","18.245.46.4","18.245.46.6"]}00
acata.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 20018.245.46.117US{"github":["https://github.com/puremourning/vimspector","https://github.com/madzak/python-json-logger","https://github.com/googleapis/python-container/issues/6"]}2026-04-23AWS Certificate Manager, Amazon CloudFront, Amazon Web Services, Facebook Pixel, Google Analytics, Google Tag Manager, HSTS, Hatena Blog, Microsoft Clarity, Nginx2026-06-05TRUE{"A":["18.245.46.117","18.245.46.2","18.245.46.4","18.245.46.6"]}00
akagenoakisan.hatenadiary.jphatenadiary.jpjpPRIVATEHTTP 40418.245.46.117US{"facebook":["https://facebook.com/hatenablog"],"x-twitter":["https://twitter.com/hatenablog"]}2026-04-24HSTS, Nginx, jQuery, Twitter, Varnish, Open Graph, Hatena Blog, Twitter Ads, Facebook Pixel, Google Analytics2026-05-28TRUE{"A":["18.245.46.117","18.245.46.2","18.245.46.4","18.245.46.6"]}002026-03-18WHOIS{"raw_response":"\r\nCannot process your search request.\r\n\r\nService currently unavailable due to incoming of a large amount of\r\nrequests.\r\n\r\nTry again later.\r\n\r\nFor details, see: https://jprs.jp/about/dom-search/whois/\r\n\r\n[ JPRS WHOIS LEGAL DISCLAIMER: ]\r\n[ ]\r\n[ The WHOIS service (the \"Service\") offered by Japan Registry Services Co., ]\r\n[ Ltd. (JPRS) and the access to the records in the JPRS WHOIS database (the ]\r\n[ \"Database\") are provided for information purposes and query-based public ]\r\n[ access. ]\r\n[ ]\r\n[ Neither JPRS nor any of its officers, directors, employees or agents ]\r\n[ makes any warranty as to the results to be obtained from use of the ]\r\n[ Service. JPRS specifically disclaims all warranties of any kind, ]\r\n[ whether express, implied or statutory, including, but not limited to, ]\r\n[ any warranties of title, non-infringement, merchantability or fitness ]\r\n[ for a particular purpose. ]\r\n[ In no event shall JPRS nor anyone else involved in creating, supporting, ]\r\n[ producing or delivering the Service be liable to you for any lost ]\r\n[ profits or costs, even if JPRS or such person has been advised of the ]\r\n[ possibility of such damages. ]\r\n[ ]\r\n[ JPRS allows you to use the Service only for lawful purposes and that, ]\r\n[ under no circumstances shall you use the Service to: (a) allow, enable ]\r\n[ or otherwise support the transmission by e-mail, telephone, postal mail, ]\r\n[ facsimile or other means of mass unsolicited, commercial advertising or ]\r\n[ solicitations to entities other than the data recipient's own existing ]\r\n[ customers; or (b) enable high volume, automated, electronic processes ]\r\n[ that send queries or data to the systems of any registry operator or ]\r\n[ ICANN-accredited registrar, except as reasonably necessary to register ]\r\n[ domain names or modify existing registrations. ]\r\n[ ]\r\n[ By submitting the query you agree to abide by these terms and further ]\r\n[ agree that JPRS may take measures to limit the use of the Service in ]\r\n[ order to protect the privacy of its registrants or the integrity of ]\r\n[ the Database. ]\r\n[ ]\r\n[ JPRS reserves the right to modify or change these terms at any time ]\r\n[ without prior or subsequent notification of any kind. ]\r\n[ ]\r\n[ For further information, use 'whois -h whois.jprs.jp help'. ]\r\n[ To express Japanese output, add '/j' at the end of command, ]\r\n[ e.g. 'whois -h whois.jprs.jp xxx/j'. ]\r\n[ ]\r\n[ For more information on Whois status codes, please visit ]\r\n[ https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en. ]\r\n"}Domain is active
Showing 5 of 585 rows · All active domains · Every live domain with its TLD and domain type.

The .hatenadiary.jp dataset

Everything we have on 585 .hatenadiary.jp domains in one downloadable file — fresh export every day. Same columns and cadence as any top-level TLD.

Buy a dataset to download .hatenadiary.jp

The full .hatenadiary.jp slice (4.3 KB JSONL, fresh daily exports) lives inside each dataset. Buy one — €29 to €599 / month — and download immediately. No subscription.

See datasets ↓ Download free preview (20 rows)

Frequently asked questions

How many .hatenadiary.jp domains are there?

webatla tracks 585 active .hatenadiary.jp domains, re-exported every day — each with its DNS, RDAP/WHOIS, detected technologies, IP, hosting country and ranking.

Can I download the full list of .hatenadiary.jp domains?

Yes — the full .hatenadiary.jp list downloads as structured JSONL (zstd). Pay once for one month, no subscription; a free sample is available first.

What's included for each domain, and how fresh is it?

Every domain carries the full schema — DNS, RDAP/WHOIS, technologies, IP & country, PageRank and Harmonic — re-exported daily.