raysafe.jp - dns.ninja
raysafe.jp
| DNSSEC | ⚠️ Not signed | ||||||
| A | 217.19.248.132🇬🇧 SAFENAMES-AS217.19.248.0/24 Safenames Datacentre | ||||||
| PTR | redirect.idp365.net | ||||||
| NS | dns1.safenames.com ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:3084🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.48.132Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | dns1.safenames.com | ||||||
| NS | dns2.safenames.net | ||||||
| A | 2400:cb00:2049:1::a29f:31aa🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.49.170Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | dns2.safenames.net | ||||||
| NS | dns3.safenames.org | ||||||
| A | 2400:cb00:2049:1::ac40:3017🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 172.64.48.23🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | dns3.safenames.org | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | dns1.safenames.comhostmaster@safenames.net 2019-12-11 #0 | ||||||
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=1782857702 | ||||||
Same first word
Similar names
easyfar.com |
syaerfa.com |
yafesar.appspot.com |
sferaya.ru |
fearsay.com |
saferay.com |
aysearf.com |
safarey.com |
fareasy.com |
yesafar.com |
DNS History
10 records (4 active, 6 former)
●NSdns1.safenames.com2026-06-14 → 2026-06-30 · 3 obs
● 2026-06-14 23:54:28
● 2026-06-30 22:34:58
●NSdns2.safenames.net2026-06-14 → 2026-06-30 · 3 obs
● 2026-06-14 23:54:28
● 2026-06-30 22:34:58
●NSdns3.safenames.org2026-06-14 → 2026-06-30 · 3 obs
● 2026-06-14 23:54:28
● 2026-06-30 22:34:58
○NSns1.p07.dynect.net2015-08-22 → 2017-05-30 · 4 obs
● 2017-05-30 13:59:46
○ 2026-06-14 23:54:28
○ 2026-06-30 22:34:58
○NSns2.p07.dynect.net2015-08-22 → 2017-05-30 · 4 obs
● 2017-05-30 13:59:46
○ 2026-06-14 23:54:28
○ 2026-06-30 22:34:58
○NSns3.p07.dynect.net2015-08-22 → 2017-05-30 · 4 obs
● 2017-05-30 13:59:46
○ 2026-06-14 23:54:28
○ 2026-06-30 22:34:58
○NSns4.p07.dynect.net2015-08-22 → 2017-05-30 · 4 obs
● 2017-05-30 13:59:46
○ 2026-06-14 23:54:28
○ 2026-06-30 22:34:58
○A216.146.46.102015-08-22 → 2017-05-30 · 4 obs
● 2017-05-30 13:59:46
○ 2026-06-14 23:54:28
○ 2026-06-30 22:34:58
○A216.146.46.112015-08-22 → 2017-05-30 · 4 obs
● 2017-05-30 13:59:46
○ 2026-06-14 23:54:28
○ 2026-06-30 22:34:58
●A217.19.248.1322026-06-14 → 2026-06-30 · 3 obs
● 2026-06-14 23:54:28
● 2026-06-30 22:34:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | c.dns.jp, h.dns.jp, e.dns.jp, g.dns.jp... | - |
| raysafe.jp | dns2.safenames.net, dns3.safenames.org, dns1.safenames.com | - |
✅ Authoritative Response
Server:162.159.48.132
NS records: dns2.safenames.net, dns3.safenames.org, dns1.safenames.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for raysafe.jp (unsigned zone)
⏱️ Timing
Total: 363ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 217.19.248.132 |
| NS | 3 | dns1.safenames.com, dns2.safenames.net... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | dns1.safenames.com hostmaster.safenames. |
Analysis
IP Addresses
raysafe.jp has exactly one IP address — 217.19.248.132.
calculnutritif.ca, servicecarerates.mercedes-benz.co.uk, dell-moscow.com plus two other host names have IP numbers in common with raysafe.jp.
Name Servers
raysafe.jp is delegated to three name servers: dns1.safenames.com, dns2.safenames.net and dns3.safenames.org.
The name servers of raysafe.jp overlap at least partially with those of other domains — among them galacticresistancegame.com, steamcommunities.biz, wsrglobal.com and two more.
dns1.safenames.com, dns2.safenames.net and dns3.safenames.org each resolve to two IP addresses: dns1.safenames.com resolves to 162.159.48.132 and 2400:cb00:2049:1::a29f:3084; dns2.safenames.net resolves to 162.159.49.170 and 2400:cb00:2049:1::a29f:31aa; dns3.safenames.org resolves to 172.64.48.23 and 2400:cb00:2049:1::ac40:3017.