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 ⚠️ Not in parent delegation | ||||||
| NS | e.tld.ma | ||||||
| NS | f.tld.ma | ||||||
| NS | ns-ma.nic.fr ⚠️ Not in parent delegation | ||||||
| SOA | c.tld.mama@anrt.ma serial=2039308654 | ||||||
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
13 records (11 active, 2 former)
●NSeloise.ns.cloudflare.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●NSkeenan.ns.cloudflare.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●MXalt1.aspmx.l.google.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●MXalt2.aspmx.l.google.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●MXalt3.aspmx.l.google.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●MXalt4.aspmx.l.google.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●MXaspmx.l.google.com2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●A104.21.8.592026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
○A172.64.80.12026-03-27 → 2026-06-08 · 2 obs
○ 2026-06-08 14:30:02
●A172.67.138.1542026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
○A2606:4700:130:436c:6f75:6466:6c61:72652026-03-27 → 2026-06-08 · 2 obs
○ 2026-06-08 14:30:02
●A2606:4700:3036::6815:83b2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
●A2606:4700:3036::ac43:8a9a2026-03-27 → 2026-06-08 · 2 obs
● 2026-06-08 14:30:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ma | a.tld.ma, b.tld.ma, c.tld.ma, d.tld.ma... | 18 records |
| hellosafe.ma | eloise.ns.cloudflare.com, keenan.ns.cloudflare.com | - |
✅ Authoritative Response
Server:108.162.195.11
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: 577ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.8.59, 172.67.138.154 |
| AAAA | 2 | 2606:4700:3036::ac43:8a9a, 2606:4700:3036::6815:83b |
| 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. |
📌 Glue Records Collected
Total: 18
In-bailiwick: 15 (a.tld.ma, a.tld.ma, b.tld.ma...)
Out-of-bailiwick: 3 (dns.inria.fr, ns-ma.nic.fr, ns-ma.nic.fr)
Analysis
IP Addresses
hellosafe.ma resolves to 4 IP numbers: 104.21.8.59, 172.67.138.154, 2606:4700:3036::6815:83b and 2606:4700:3036::ac43:8a9a.
Additional host names — nextalp.com, wxjiqi.com, trusttravelhub.shop 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 haichunddm.com, linearroles.com, pure-crete.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 lex.ns.cloudflare.com.
Host names with 6 IP numbers:
eloise.ns.cloudflare.com directs to 108.162.194.208, 162.159.38.208, 172.64.34.208 and three others.
keenan.ns.cloudflare.com directs to 108.162.195.11, 162.159.44.11, 172.64.35.11 and three others.
Mail Servers
hellosafe.ma is handled by 5 mail servers: 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 74.125.137.27 and 2607:f8b0:4023:c06::1a.
alt1.aspmx.l.google.com resolves to 172.217.216.26 and 2607:f8b0:4023:2803::1a.
alt2.aspmx.l.google.com resolves to 172.253.145.27 and 2607:f8b0:4023:3003::1a.
alt3.aspmx.l.google.com resolves to 172.253.135.26 and 2607:f8b0:4023:1015::1b.
alt4.aspmx.l.google.com resolves to 173.194.42.26 and 2607:f8b0:4001:c79::1a.