The domain cdatablog.jp is registered with an undisclosed registrar. Email delivery is handled by No MX Records Found. No valid SPF record was detected. DMARC protection is missing or unconfigured.
Domain Overview: cdatablog.jp
Expires in N/A · DNSSEC: Unsigned
No MX Records Found
Issuer: N/A
N/A
🌐 Domain & Registration Identity View Full Whois Details →
| Domain | cdatablog.jp |
|---|---|
| Website Title | |
| Registered | N/A |
| Expires | N/A |
| Remaining Validity | N/A |
| Domain Age | N/A |
| Registrar | N/A |
| Domain Status | N/A |
| DNSSEC Delegation | Unsigned · Zone not signed with DNSSEC keys |
| Authoritative Nameservers |
01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp
|
🛡️ Email Security & Deliverability (SPF, DKIM, DMARC) View Complete Email Security Diagnostics →
| Detected Email Provider | 📬 No MX Records Found |
|---|---|
| Primary Mail Server (MX) |
None
|
| SPF Record (Sender Policy) | Missing |
| DKIM Authentication | Not Detected · (No common third-party selector found; custom keys may be configured) |
| DMARC Policy | Missing |
| SMTP Port 25 Status | N/A · Inbound mail server handshake response |
🖥️ Web Server, Hosting & Network View Full Server & Tech Details →
| Web Server Software | N/A |
|---|---|
| HTTP Status Code | N/A |
| Server IP (IPv4) | N/A View Geo Details → |
| IPv6 Address (AAAA) | Not Configured |
| Reverse DNS (PTR) |
None Detected (No PTR Record)
|
| Server Location | 📍 N/A |
| ASN Network & ISP | N/A |
| Hosting Provider | N/A |
| Control Panel | Not Detected |
| Technology Stack | No third-party framework or CMS fingerprints detected |
| HTTP Security Headers | None Detected (Missing HSTS / CSP) Audit Details → |
| DNSBL Blacklist Reputation | Clean (0/5 lists) |
🔒 SSL/TLS Certificate Summary View Full SSL Certificate & Chain →
| Primary Hostname (CN) | N/A |
|---|---|
| SSL Issuer | N/A |
| SSL Valid Till | N/A |
| Remaining Validity | N/A Days |
| Chain Status | Invalid / Untrusted |
| Signature Algorithm | N/A |
Whois Ownership & Registration for cdatablog.jp
📄 View Raw Registry Response ↓Domain Information
Registrar Information
Registrant Contact
Contact information for this role is not provided or redacted.
Administrative Contact
Contact information for this role is not provided or redacted.
Technical Contact
Contact information for this role is not provided or redacted.
📄 View Raw Registry Response Legacy Whois (Port 43)
[ 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] CDATABLOG.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] 01.dnsv.jp
[Name Server] 02.dnsv.jp
[Name Server] 03.dnsv.jp
[Name Server] 04.dnsv.jp
[Signing Key]
[登録年月日] 2018/11/05
[有効期限] 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] cdatablog.jp@whoisprotectservice.com
[Web Page]
[郵便番号] 150-8512
[住所] 東京都渋谷区
桜丘町 26-1
セルリアンタワー 11階
[Postal Address] Shibuya-ku
26-1 Sakuragaoka-cho
Cerulean Tower 11F
[電話番号] +81.354562560
[FAX番号]
DNS Records for cdatablog.jp
NS Records
| Name | Data | Copy |
|---|---|---|
| cdatablog.jp. | 01.dnsv.jp. |
|
| cdatablog.jp. | 02.dnsv.jp. |
|
| cdatablog.jp. | 03.dnsv.jp. |
|
| cdatablog.jp. | 04.dnsv.jp. |
A Records
No A records found.
AAAA Records
No AAAA records found.
WWW Records (www.cdatablog.jp)
| Type | Host | Value | Copy |
|---|---|---|---|
| CNAME | www.cdatablog.jp. | hatenablog.com. |
|
| A | www.cdatablog.jp. | hatenablog.com. |
|
| A | hatenablog.com. | 108.159.28.46 |
|
| A | hatenablog.com. | 108.159.28.68 |
|
| A | hatenablog.com. | 108.159.28.128 |
|
| A | hatenablog.com. | 108.159.28.61 |
MX Records
No MX records found.
TXT Records
No TXT records found.
Email Security (MX, SPF, DKIM, DMARC, SMTP) for cdatablog.jp
Mail Exchange (MX) Routing Records
Warning: No MX records were found for cdatablog.jp. This domain cannot receive emails.
SPF Record Validation
No SPF record found to validate.
Common DKIM Selectors
No common third-party DKIM selectors found. Custom selectors may be configured.
🔍 Query Custom DKIM Selector
Live DNS Lookup
Using a custom or date-based selector (e.g. crm, newsletter, 2024)? Query its public key live on cdatablog.jp:
DMARC Policy Validation
No DMARC record found to validate.
Validation Summary
| DMARC Record Published | Fail No DMARC record was found. |
Optimization Suggestions
A DMARC record is essential for email security. It tells receiving servers what to do with emails that fail SPF and DKIM checks, protecting your domain from spoofing.
Server IP Blacklist Check ()
SSL/TLS Certificate Details for cdatablog.jp
Could not connect to get SSL certificate.
Website & Server Intelligence for cdatablog.jp
Website Identity
| Title | |
|---|---|
| Meta Description | N/A |
Hosting & Server Network
| IP Address | N/A |
|---|---|
| HTTP Status | N/A |
| Hosting Provider | N/A |
| Web Server | N/A |
| Control Panel | Not Detected |
Technology Profile
No specific third-party frameworks or CMS fingerprints detected.
HTTP Security Headers
Could not fetch HTTP headers.
IP Details & Geolocation
Could not retrieve detailed IP information.
Understanding Diagnostic Terms for cdatablog.jp
Domain Status (EPP)
EPP status codes (e.g., clientTransferProhibited, active) indicating if a domain is locked against unauthorized transfer, pending renewal, or active.
Registrar Information
The authorized or accredited organization managing the domain reservation and authoritative registry delegation.
Nameservers (NS)
Authoritative servers that translate domain names into IP addresses and direct web visitors and mail traffic globally.
A & AAAA Records
Primary address records mapping your domain name directly to standard IPv4 (e.g., 192.0.2.1) and newer IPv6 server network addresses.
MX (Mail Exchange)
Priority-ranked records pointing inbound emails to designated mail server hosts (e.g., Google Workspace, Microsoft 365, Zoho).
SPF & DMARC Security
Email authentication standards that verify authorized sender IPs (SPF) and instruct receiving servers how to enforce security policies (DMARC).
DKIM Signatures
Cryptographic public key in DNS used by receiving mail servers to verify digital signatures on your emails, ensuring messages were not tampered with.
SSL Certificate & Chain
Establishes encrypted HTTPS connections and authenticates domain ownership via an intermediate certificate authority chain.
Hosting Provider & ASN
The physical server infrastructure where website files reside and the autonomous system network (ASN) routing global traffic.
Reverse DNS (PTR)
Pointer (PTR) records that map a server's IP address back to its canonical hostname, verifying server identity and preventing email spam rejection.
HTTP Security Headers
Directives like HSTS, CSP, and X-Frame-Options instructed by the server to protect browser visitors against XSS, clickjacking, and packet sniffing.
⚠️ Report Limitations & Data Sources
- Data Currency: This report uses cached registry and DNS data (freshened within 4 hours) for high-speed resolution. Click "🔄 Refresh Live" to query directly against authoritative registries.
- DNS Resolution & Propagation: Records are queried via Google Public DNS-over-HTTPS. Global DNS propagation may take up to 24–48 hours across different regional ISP resolvers during recent DNS record changes.
- Completeness & Scope: This diagnostic tool analyzes standard authoritative records (A, AAAA, MX, NS, TXT, CNAME, SOA). It does not perform invasive brute-force subdomain scans or unauthenticated DNS zone transfers.
- Email Deliverability & Reputation: The security analysis (SPF, DKIM, DMARC, and Port 25 SMTP handshake) reflects public DNS policies and inbound connection states. Recipient spam filters evaluate internal headers that cannot be checked from outside.
- Reverse Proxies & CDNs: If a website is behind Cloudflare, Fastly, or another CDN/reverse proxy, the detected IP, web server software, and SSL edge certificate reflect the proxy tier.