rubycurrant.com - dns.ninja
rubycurrant.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1788604833 | ||||||
MX for
rubycurrant.com |
Same first word
rubycurrant.com |
Previous names
Next names
DNS History
7 records (7 active, 0 former)
●NSns1.xserver.jp2026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
●NSns2.xserver.jp2026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
●NSns3.xserver.jp2026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
●NSns4.xserver.jp2026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
●NSns5.xserver.jp2026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
●MXrubycurrant.com2026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
●A162.43.94.2002026-09-03 → 2026-09-05 · 2 obs
● 2026-09-05 10:54:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| rubycurrant.com | ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp... | - |
✅ Authoritative Response
Server:157.112.182.218
NS records: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rubycurrant.com (unsigned zone)
⏱️ Timing
Total: 1222ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.43.94.200 |
| NS | 5 | ns4.xserver.jp, ns3.xserver.jp... |
| MX | 1 | rubycurrant.com (pri: 0) |
| TXT | 1 | v=spf1 +a:sv16059.xserver.jp +a:rubycurr |
| SOA | 1 | ns1.xserver.jp root.xserver.jp |
Analysis
Mail Server Role
rubycurrant.com handles its own mail, functioning as its own mail server.
IP Addresses
rubycurrant.com resolves to just one IP address, 162.43.94.200.
Two other host names, along with okutatsu.com, it-clip.net and petmemoryart.jp, also share IP numbers with rubycurrant.com.
Name Servers
rubycurrant.com delegates to five name servers: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp and two others.
rubycurrant.com has at least partial name server overlap with other domains, such as akaneiro-stage.com, dtminfo.com, disk-rescue.jp and two others.
It is common to see these name servers used together with name servers ns4.xserver.jp and ns5.xserver.jp.
Hostnames that map to three IP numbers:
ns1.xserver.jp resolves to 202.226.36.164, 202.226.36.170 and 202.226.36.246.
ns4.xserver.jp resolves to 183.90.224.226, 183.90.224.230 and 202.226.39.247.
ns5.xserver.jp resolves to 157.112.182.218, 157.112.182.220 and 202.226.37.247.
Host names that point to one IP address:
ns2.xserver.jp resolves to 35.72.43.26.
ns3.xserver.jp resolves to 202.226.36.247.
Mail Servers
rubycurrant.com is served by just one mail server: rubycurrant.com.
rubycurrant.com points to one IP number — 162.43.94.200.