informationsecurity.mx - dns.ninja
informationsecurity.mx
| 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 | ||||||
| SOA | dns1.safenames.comhostmaster@safenames.net 2024-07-05 #0 | ||||||
mx
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | m.mx-ns.mx ⭐ | ||||||
| NS | c.mx-ns.mx | ||||||
| NS | e.mx-ns.mx | ||||||
| NS | i.mx-ns.mx | ||||||
| NS | o.mx-ns.mx | ||||||
| NS | x.mx-ns.mx | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1785344435 | ||||||
Same first word
Similar names
DNS History
5 records (4 active, 1 former)
●NSdns1.safenames.com2026-07-13 → 2026-07-29 · 2 obs
● 2026-07-29 17:04:24
●NSdns2.safenames.net2026-07-13 → 2026-07-29 · 2 obs
● 2026-07-29 17:04:24
●NSdns3.safenames.org2026-07-13 → 2026-07-29 · 2 obs
● 2026-07-29 17:04:24
○A198.57.247.1772015-07-02 → 2018-08-21 · 4 obs
● 2018-08-21 05:53:20
○ 2026-07-13 10:49:08
○ 2026-07-29 17:04:24
●A217.19.248.1322026-07-13 → 2026-07-29 · 3 obs
● 2026-07-13 10:49:08
● 2026-07-29 17:04:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx... | - |
| informationsecurity.mx | dns1.safenames.com, dns2.safenames.net, dns3.safenames.org | - |
✅ Authoritative Response
Server:172.64.48.23
NS records: dns1.safenames.com, dns2.safenames.net, dns3.safenames.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for informationsecurity.mx (unsigned zone)
⏱️ Timing
Total: 2268ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 217.19.248.132 |
| NS | 3 | dns1.safenames.com, dns3.safenames.org... |
| SOA | 1 | dns1.safenames.com hostmaster.safenames. |
Analysis
IP Addresses
informationsecurity.mx resolves to just one IP address, 217.19.248.132.
Two other host names, along with jcb.academy, mercedes-benzvanservicing.co.uk and clinicaldepressionstudies.com, also share IP numbers with informationsecurity.mx.
Name Servers
Three name servers are authoritative for informationsecurity.mx: dns1.safenames.com, dns2.safenames.net and dns3.safenames.org.
informationsecurity.mx partially shares its NS delegation with several other domains, including formulex.eu, europa-safety.com, upoldo.com and two others.
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. All three hostnames point to two IP numbers each.