sed.jp is registered with whois.jprs.jp and is hosted on AS2514 in Japan. Its SSL certificate from Let's Encrypt is valid until 11 Jan 2027, and the site does not support HTTP/3.
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.
0 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 sed.jp’s name taken on other extensions?
Every IP address sed.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| sed.jp | 163.44.0.165 | 3600 |
| Host | Name server | TTL |
|---|---|---|
| sed.jp | 01.dnsv.jp | 86400 |
| sed.jp | 02.dnsv.jp | 86400 |
| sed.jp | 03.dnsv.jp | 86400 |
| sed.jp | 04.dnsv.jp | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| sed.jp | 01.dnsv.jp hostmaster.dnsv.jp 1724178885 3600 900 604800 300 | 86400 |
No reviews yet. Used sed.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.
sed.jp has no community safety rating yet. Its SSL certificate is valid until 11 Jan 2027. See Security →
sed.jp is registered through whois.jprs.jp. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
sed.jp is served from 1 IP address, mainly on AS2514 in Japan. See Hosting →
Raw registry data for sed.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] SED.JP
[登録者名] （登録者からの申請により非表示）
詳細は→https://jprs.jp/about/dom-rule/whois-concealment/
[Registrant] (Not displayed by registrant's request)
For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese)
[Name Server] 03.dnsv.jp
[Name Server] 02.dnsv.jp
[Name Server] 01.dnsv.jp
[Name Server] 04.dnsv.jp
[Signing Key]
[登録年月日] 2016/11/04
[有効期限] 2026/11/30
[状態] Active
[最終更新] 2025/12/01 01:05:04 (JST)
Contact Information: [公開連絡窓口]
[名前] Whois情報公開代行サービス by お名前.com
[Name] Whois Privacy Protection Service by onamae.com
[Email] [email protected]
[Web Page]
[郵便番号] 150-8512
[住所] 東京都渋谷区
桜丘町 26-1
セルリアンタワー 11階
[Postal Address] Shibuya-ku
26-1 Sakuragaoka-cho
Cerulean Tower 11F
[電話番号] +81.354562560
[FAX番号]Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with sed.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://sed.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 25 Oct 2026.