keepersecurity.jp - dns.ninja
keepersecurity.jp
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1782465302 | ||||||
📈 Tranco rank: #406,210
Subdomains
Same first word
keepersecurity.me |
keepersecurity.co |
keepersecurity.jp |
keepersecurity.info |
keepersecurity.eu |
keepersecurity.org |
keepersecurity.com.au |
keepersecurity.net |
keepersecurity.ca |
keepersecurity.com |
keepersecurity.us |
Similar names
DNS History
11 records (11 active, 0 former)
●NSns-11.awsdns-01.com2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●NSns-1229.awsdns-25.org2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●NSns-1765.awsdns-28.co.uk2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●NSns-572.awsdns-07.net2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●MXalt1.aspmx.l.google.com2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●MXalt2.aspmx.l.google.com2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●MXalt3.aspmx.l.google.com2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●MXalt4.aspmx.l.google.com2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●MXaspmx.l.google.com2026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●A13.159.229.22026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
●A18.177.159.1722026-02-17 → 2026-06-26 · 2 obs
● 2026-06-26 10:07:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | f.dns.jp, a.dns.jp, b.dns.jp, d.dns.jp... | - |
| keepersecurity.jp | ns-572.awsdns-07.net, ns-11.awsdns-01.com, ns-1765.awsdns-28.co.uk, ns-1229.awsdns-25.org | - |
✅ Authoritative Response
Server:205.251.198.229
NS records: ns-572.awsdns-07.net, ns-11.awsdns-01.com, ns-1765.awsdns-28.co.uk, ns-1229.awsdns-25.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for keepersecurity.jp (unsigned zone)
⏱️ Timing
Total: 2948ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.159.229.2, 18.177.159.172 |
| NS | 4 | ns-11.awsdns-01.com, ns-1229.awsdns-25.org... |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 2 | google-site-verification=1AmdZJTsVGbynoz, v=spf1 include:amazonses.com include:_sp |
| SOA | 1 | ns-572.awsdns-07.net awsdns-hostmaster.a |
Analysis
Hierarchy
www.keepersecurity.jp, qa.keepersecurity.jp and dev.keepersecurity.jp each fall under the parent domain keepersecurity.jp.
IP Addresses
keepersecurity.jp directs to two IP numbers, 13.159.229.2 and 18.177.159.172
ec2-18-177-159-172.ap-northeast-1.compute.amazonaws.com and www.keepersecurity.jp, along with other host names, share IP addresses with keepersecurity.jp.
Name Servers
The domain keepersecurity.jp is delegated to these four name servers: ns-11.awsdns-01.com, ns-572.awsdns-07.net, ns-1229.awsdns-25.org and ns-1765.awsdns-28.co.uk.
keepersecurity.jp partially shares its NS delegation with several other domains, including loveisdinww.isdin.com, test.ramseysolutions.net, aspect-online.eu and two others.
ns-11.awsdns-01.com, ns-572.awsdns-07.net, ns-1229.awsdns-25.org and ns-1765.awsdns-28.co.uk each carry two IP addresses. ns-11.awsdns-01.com has 205.251.192.11 and 2600:9000:5300:b00::1; ns-572.awsdns-07.net has 205.251.194.60 and 2600:9000:5302:3c00::1; ns-1229.awsdns-25.org has 205.251.196.205 and 2600:9000:5304:cd00::1; ns-1765.awsdns-28.co.uk has 205.251.198.229 and 2600:9000:5306:e500::1.
Mail Servers
Mail for keepersecurity.jp is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
keepersecurity.jp shares at least some of its mail servers with other domains — for example counselinghelp.net, pontofrio.pt, rocf.org and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.