lezhin.jp - robtex.com
Search for stuff
lezhin.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=1770936303 | ||||||
Up
www.lezhin.jp |
Same first word
Similar names
heinzl.at |
lizhen.me |
heinzl.net |
zhenli.name |
linzhe.net |
lheinz.net |
heinzl.eu |
heinzl.ch |
lheinz.com |
heinzl.com |
lheinz.at |
hzenli.com |
lizhen.net.cn |
hzline.com |
zhenli.mobi |
hinzel.de |
heinzl.org |
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| lezhin.jp | ns-506.awsdns-63.com, ns-1513.awsdns-61.org | - |
✅ Authoritative Response
Server: 205.251.197.233
NS records: ns-506.awsdns-63.com, ns-1513.awsdns-61.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for lezhin.jp (unsigned zone)
⏱️ Timing
Total: 147ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.195.60.165, 13.231.26.70 |
| NS | 4 | ns-1513.awsdns-61.org, ns-1912.awsdns-47.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 3 | google-site-verification=0dn7EKVJVuj_Vrf, google-site-verification=Ip7iYFlwQ93e4wk... |
| SOA | 1 | ns-506.awsdns-63.com awsdns-hostmaster.a |
AI analysis
lezhin.jp is the parent of www.lezhin.jp.
lezhin.jp resolves to two IP numbers: 13.231.26.70 and 52.195.60.165.
Other host names such as ec2-52-195-60-165.ap-northeast-1.compute.amazonaws.com and ec2-13-231-26-70.ap-northeast-1.compute.amazonaws.com share IP numbers with lezhin.jp.
lezhin.jp is delegated to four name servers: ns-506.awsdns-63.com, ns-954.awsdns-55.net, ns-1513.awsdns-61.org and ns-1912.awsdns-47.co.uk.
lezhin.jp at least partially shares name servers with other domains, for instance discoverydigital.org, arteccrm.com, splashpiscinas.com.br, d1nfu7x7ctx7oi.cloudfront.net and avvocatodemichele.it.
Name servers commonly used together include ns-852.awsdns-42.net, ns-1504.awsdns-60.org, ns-1767.awsdns-28.co.uk, ns-1203.awsdns-22.org, ns-1946.awsdns-51.co.uk, ns-1422.awsdns-49.org, ns-279.awsdns-34.com, ns-1204.awsdns-22.org and ns-1622.awsdns-10.co.uk.
Host names with two IP numbers:
ns-506.awsdns-63.com points to 2600:9000:5301:fa00::1 and 205.251.193.250; ns-954.awsdns-55.net points to 2600:9000:5303:ba00::1 and 205.251.195.186; ns-1513.awsdns-61.org points to 2600:9000:5305:e900::1 and 205.251.197.233; ns-1912.awsdns-47.co.uk points to 2600:9000:5307:7800::1 and 205.251.199.120.
lezhin.jp is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
lezhin.jp shares some mail servers with other domains, at least partially, for instance ogastudio.com, iut-dhaka.edu, ns500758.ns500759.ns500759.ns500698.ns500735.ns500735.ns500736.ns500698.ns500698.ns500736.ns500698.ns500698.ns500698.ns500698.ns500576.ns500698.ns500576.trackreceptor.com, ns500699.ns500693.ns500693.ns500693.ns500734.ns500699.ns500699.ns500693.ns500699.ns500699.ns500734.ns500699.ns500588.ns500588.ns500588.ns500588.ns500110.dtrkdll.com and ns500671.ns500731.ns500754.ns500754.ns500754.ns500742.ns500731.ns500704.ns500742.ns500705.ns500705.ns500704.ns500678.ns500649.ns500649.ns500291.ns500153.tenderladiesbz.com.
these mail servers are often used with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx2.googlemail.com points to 2800:3f0:4003:c0f::1a and 108.177.123.27.
aspmx3.googlemail.com points to 2a00:1450:400b:c02::1a and 172.253.116.26.
aspmx.l.google.com points to 2607:f8b0:4023:2801::1a and 142.250.115.27.
alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.27.
Host names that point to 2a00:1450:400b:c02::1a: aspmx3.googlemail.com and alt2.aspmx.l.google.com.