veet.jp - robtex.com
veet.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=1783323002 | ||||||
Same first word
Similar names
DNS History
14 records (5 active, 9 former)
○NSa4.nstld.com2008-11-25 → 2017-07-01 · 4 obs
● 2017-07-01 21:01:38
○ 2026-06-22 16:51:48
○ 2026-07-06 07:36:36
○NSf4.nstld.com2008-11-25 → 2017-07-01 · 4 obs
● 2017-07-01 21:01:38
○ 2026-06-22 16:51:48
○ 2026-07-06 07:36:36
○NSg4.nstld.com2008-11-25 → 2017-07-01 · 4 obs
● 2017-07-01 21:01:38
○ 2026-06-22 16:51:48
○ 2026-07-06 07:36:36
●NSha1.markmonitor.zone2026-06-22 → 2026-07-06 · 3 obs
● 2026-06-22 16:51:48
● 2026-07-06 07:36:36
●NSha2.markmonitor.zone2026-06-22 → 2026-07-06 · 3 obs
● 2026-06-22 16:51:48
● 2026-07-06 07:36:36
●NSha3.markmonitor.zone2026-06-22 → 2026-07-06 · 3 obs
● 2026-06-22 16:51:48
● 2026-07-06 07:36:36
●NSha4.markmonitor.zone2026-06-22 → 2026-07-06 · 3 obs
● 2026-06-22 16:51:48
● 2026-07-06 07:36:36
○NSl4.nstld.com2008-11-25 → 2008-11-25 · 3 obs
○ 2015-07-25 23:42:44
○ 2026-07-06 07:36:36
○MXrelay1.netnames.net2008-11-25 → 2017-07-01 · 4 obs
● 2017-07-01 21:01:38
○ 2026-06-22 16:51:48
○ 2026-07-06 07:36:36
○MXrelay2.netnames.net2008-11-25 → 2017-07-01 · 4 obs
● 2017-07-01 21:01:38
○ 2026-06-22 16:51:48
○ 2026-07-06 07:36:36
●A34.54.78.1012026-06-22 → 2026-07-06 · 3 obs
● 2026-06-22 16:51:48
● 2026-07-06 07:36:36
○A52.50.117.612016-04-02 → 2017-07-01 · 5 obs
● 2016-04-02 10:10:26
● 2017-07-01 21:01:38
○ 2026-06-22 16:51:48
○ 2026-07-06 07:36:36
○A72.3.222.1792008-11-25 → 2008-11-25 · 3 obs
○ 2015-07-25 23:42:44
○ 2026-07-06 07:36:36
○A83.231.200.1032015-07-25 → 2016-03-09 · 5 obs
● 2015-07-25 23:42:44
● 2016-03-09 09:47:34
○ 2016-04-02 10:10:26
○ 2026-07-06 07:36:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | g.dns.jp, e.dns.jp, b.dns.jp, a.dns.jp... | - |
| veet.jp | ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone | - |
✅ Authoritative Response
Server:162.219.55.170
NS records: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for veet.jp (unsigned zone)
⏱️ Timing
Total: 1424ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.54.78.101 |
| NS | 4 | ha2.markmonitor.zone, ha1.markmonitor.zone... |
| TXT | 2 | aq0t0agfcdfod9pjdtjtte5kq0, google-site-verification=1gagDv7DElUEGP3 |
| SOA | 1 | ha1.markmonitor.zone hostmaster.markmoni |
Analysis
IP Addresses
veet.jp points to a single IP number: 34.54.78.101.
Additional host names — olla.com.br, www.veet.com.tr, www.olla.com.br and two others — share IP numbers with veet.jp.
Name Servers
veet.jp has four authoritative name servers: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone.
At least some of veet.jp's name servers are shared with other domains, for example splunkmobile.cn, crozerbenefits.org, octaplaslg.co.za and two more.
These name servers tend to co-occur with ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 other name servers in the same DNS delegations.
Four hostnames, each resolving to a pair of IP addresses: ha1.markmonitor.zone directs to 192.174.68.5 and 2001:67c:1bc::5; ha2.markmonitor.zone directs to 162.219.54.170 and 2620:10a:80eb::6b; ha3.markmonitor.zone directs to 176.97.158.5 and 2001:67c:10b8::5; ha4.markmonitor.zone directs to 162.219.55.170 and 2620:10a:80ec::6b.