hellosafe.ma - dns.ninja
hellosafe.ma
ma
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | c.tld.ma ⭐ | ||||||
| NS | a.tld.ma | ||||||
| NS | b.tld.ma | ||||||
| NS | d.tld.ma | ||||||
| NS | dns.inria.fr | ||||||
| NS | e.tld.ma | ||||||
| NS | f.tld.ma | ||||||
| NS | ns-ma.nic.fr | ||||||
| SOA | c.tld.mama@anrt.ma serial=2039522593 | ||||||
Same first word
hellosafe.be |
hellosafe.ma |
hellosafe.com.mx |
hellosafe.com |
hellosafe.fr |
hellosafe.ch |
hellosafe.com.br |
hellosafe.at |
hellosafe.it |
hellosafe.co.uk |
hellosafe.ca |
DNS History
15 records (11 active, 4 former)
●NSeloise.ns.cloudflare.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●NSkeenan.ns.cloudflare.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●MXalt1.aspmx.l.google.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●MXalt2.aspmx.l.google.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●MXalt3.aspmx.l.google.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●MXalt4.aspmx.l.google.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●MXaspmx.l.google.com2026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
●A104.21.8.592026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
○A172.64.80.12026-03-27 → 2026-08-16 · 2 obs
○ 2026-08-16 21:07:50
●A172.67.138.1542026-03-27 → 2026-08-16 · 2 obs
● 2026-08-16 21:07:50
○A2606:4700:130:436c:6f75:6466:6c61:72652026-03-27 → 2026-08-16 · 2 obs
○ 2026-08-16 21:07:50
●A2606:4700:3032::6815:83b2026-07-15 → 2026-08-16 · 3 obs
● 2026-07-15 23:09:38
● 2026-08-16 21:07:50
●A2606:4700:3033::ac43:8a9a2026-07-15 → 2026-08-16 · 3 obs
● 2026-07-15 23:09:38
● 2026-08-16 21:07:50
○A2606:4700:3036::6815:83b2026-03-27 → 2026-06-09 · 4 obs
● 2026-06-09 13:51:56
○ 2026-07-15 23:09:38
○ 2026-08-16 21:07:50
○A2606:4700:3036::ac43:8a9a2026-03-27 → 2026-06-09 · 4 obs
● 2026-06-09 13:51:56
○ 2026-07-15 23:09:38
○ 2026-08-16 21:07:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ma | b.tld.ma, d.tld.ma, f.tld.ma, c.tld.ma... | - |
| hellosafe.ma | eloise.ns.cloudflare.com, keenan.ns.cloudflare.com | - |
✅ Authoritative Response
Server:172.64.34.208
NS records: eloise.ns.cloudflare.com, keenan.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hellosafe.ma (unsigned zone)
⏱️ Timing
Total: 819ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.138.154, 104.21.8.59 |
| AAAA | 2 | 2606:4700:3032::6815:83b, 2606:4700:3033::ac43:8a9a |
| NS | 2 | eloise.ns.cloudflare.com, keenan.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 4 | google-site-verification=1evrk_lLMrRBgmp, google-site-verification=2Yl_bXylYbYcLPD... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | eloise.ns.cloudflare.com dns.cloudflare. |
Analysis
IP Addresses
hellosafe.ma directs to four IP numbers, which are 104.21.8.59, 172.67.138.154, 2606:4700:3032::6815:83b and 2606:4700:3033::ac43:8a9a.
Additional host names — nextalp.com, www.jackpotfrenzy-casino.fr, wxjiqi.com and two others — share IP numbers with hellosafe.ma.
Name Servers
hellosafe.ma has two authoritative name servers — eloise.ns.cloudflare.com and keenan.ns.cloudflare.com.
hellosafe.ma shares its name server setup with other domains, including pilatesloa.com, nbpfunds.net, hellosafe.be and two others.
At least some of hellosafe.ma's name servers are shared with other domains, for example linearroles.com, olvexa.cc, cwithelpdesk.com and two more.
It is common for these name servers to be used in conjunction with the name servers norman.ns.cloudflare.com, odin.ns.cloudflare.com and leland.ns.cloudflare.com.
Host names with 6 IP numbers:
eloise.ns.cloudflare.com points to 108.162.194.208, 162.159.38.208, 172.64.34.208 and 3 other IP addresses.
keenan.ns.cloudflare.com points to 108.162.195.11, 162.159.44.11, 172.64.35.11 and 3 other IP addresses.
Mail Servers
Five mail servers handle hellosafe.ma: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
hellosafe.ma shares mail servers — at least in part — with other domains, including ns500742.ns500742.ns500731.ns500671.ns500671.ns500754.ns500742.ns500731.ns500678.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500737.ns500724.ns500599.ns500737.ns500737.ns500599.ns500724.ns500583.ns500697.ns500583.ns500583.ns500583.yummyflingsfinder.com, ns500734.ns500699.ns500693.ns500699.ns500699.ns500734.ns500693.ns500699.ns500588.ns500588.ns500683.ns500699.ns500588.ns500693.ns500112.dtrkdll.com and two others.
These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com resolves to 172.253.115.26 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.