tinder.com.mx - dns.ninja
tinder.com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.markmonitor.com ⭐ | ||||||
| A | 2620:10a:80a8::1🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.160.1🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| NS | ns2.markmonitor.com ⚠️ Not in parent delegation | ||||||
| A | 2001:67c:10b8::1🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net | ||||||
| PTR | ns2.markmonitor.com | ||||||
| A | 176.97.158.1🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net | ||||||
| PTR | ns2.markmonitor.com | ||||||
| NS | ns3.markmonitor.com | ||||||
| A | 2620:10a:80a9::1🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.161.1🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| NS | ns4.markmonitor.com ⚠️ Not in parent delegation | ||||||
| A | 2001:67c:1bc::1🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast | ||||||
| PTR | ns1.markmonitor.com | ||||||
| A | 192.174.68.1🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net | ||||||
| PTR | ns1.markmonitor.com | ||||||
| NS | ns5.markmonitor.com ⚠️ Not in parent delegation | ||||||
| A | 2620:10a:80a8::2🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.160.2🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| NS | ns6.markmonitor.com ⚠️ Not in parent delegation | ||||||
| A | 2001:67c:10b8::3🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net | ||||||
| PTR | ns6.markmonitor.com | ||||||
| A | 176.97.158.3🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net | ||||||
| PTR | ns6.markmonitor.com | ||||||
| NS | ns7.markmonitor.com ⚠️ Not in parent delegation | ||||||
| A | 2620:10a:80a9::2🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.161.2🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| SOA | ns1.markmonitor.comhostmaster@markmonitor.com 2020-08-05 #1 | ||||||
com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | m.mx-ns.mx ⭐ ⚠️ Not in parent delegation | ||||||
| NS | c.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | e.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | i.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | o.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | x.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1786737458 | ||||||
Previously MX for
tinder.com.mx |
Same first word
Similar names
DNS History
18 records (7 active, 11 former)
○NSdns1.hospeda.mx2017-01-30 → 2017-01-30 · 4 obs
● 2017-01-30 11:57:08
○ 2026-04-08 14:16:16
○ 2026-08-14 20:03:02
○NSdns2.hospeda.mx2017-01-30 → 2017-01-30 · 4 obs
● 2017-01-30 11:57:08
○ 2026-04-08 14:16:16
○ 2026-08-14 20:03:02
○NSns1.cloudxtiny.com2016-06-25 → 2016-06-25 · 4 obs
● 2016-06-25 05:03:26
○ 2017-01-30 11:57:08
○ 2026-08-14 20:03:02
●NSns1.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
○NSns2.cloudxtiny.com2016-06-25 → 2016-06-25 · 4 obs
● 2016-06-25 05:03:26
○ 2017-01-30 11:57:08
○ 2026-08-14 20:03:02
●NSns2.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
○NSns3.cloudxtiny.com2015-08-10 → 2016-06-25 · 4 obs
● 2016-06-25 05:03:26
○ 2017-01-30 11:57:08
○ 2026-08-14 20:03:02
●NSns3.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
○NSns4.cloudxtiny.com2015-08-10 → 2016-03-06 · 4 obs
● 2016-03-06 15:46:20
○ 2016-06-25 05:03:26
○ 2026-08-14 20:03:02
●NSns4.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
●NSns5.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
●NSns6.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
●NSns7.markmonitor.com2026-04-08 → 2026-08-14 · 3 obs
● 2026-04-08 14:16:16
● 2026-08-14 20:03:02
○MXmail.tinder.com.mx2017-01-30 → 2017-01-30 · 4 obs
● 2017-01-30 11:57:08
○ 2026-04-08 14:16:16
○ 2026-08-14 20:03:02
○MXtinder.com.mx2015-08-10 → 2016-06-25 · 4 obs
● 2016-06-25 05:03:26
○ 2017-01-30 11:57:08
○ 2026-08-14 20:03:02
○A162.243.106.302017-01-30 → 2017-01-30 · 4 obs
● 2017-01-30 11:57:08
○ 2026-04-08 14:16:16
○ 2026-08-14 20:03:02
○A37.122.251.1722015-08-10 → 2016-03-06 · 4 obs
● 2016-03-06 15:46:20
○ 2016-06-25 05:03:26
○ 2026-08-14 20:03:02
○A37.122.252.1662016-06-25 → 2016-06-25 · 4 obs
● 2016-06-25 05:03:26
○ 2017-01-30 11:57:08
○ 2026-08-14 20:03:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| tinder.com.mx | ns1.markmonitor.com, ns3.markmonitor.com | - |
✅ Authoritative Response
Server:149.112.161.1
NS records: ns1.markmonitor.com, ns3.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tinder.com.mx (unsigned zone)
⏱️ Timing
Total: 473ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 7 | ns7.markmonitor.com, ns2.markmonitor.com... |
| SOA | 1 | ns1.markmonitor.com hostmaster.markmonit |
Analysis
Name Servers
tinder.com.mx has 7 name servers — ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.
The name servers of tinder.com.mx overlap at least partially with those of other domains — among them transitionsacademyvirtual.com, children-thrive.com, citypedia.com.au and two more.
These name servers commonly co-occur with the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.
Hosts with two IP numbers each:
ns1.markmonitor.com resolves to 149.112.160.1 and 2620:10a:80a8::1.
ns2.markmonitor.com resolves to 176.97.158.1 and 2001:67c:10b8::1.
ns3.markmonitor.com resolves to 149.112.161.1 and 2620:10a:80a9::1.
ns4.markmonitor.com resolves to 192.174.68.1 and 2001:67c:1bc::1.
ns5.markmonitor.com resolves to 149.112.160.2 and 2620:10a:80a8::2.
ns6.markmonitor.com resolves to 176.97.158.3 and 2001:67c:10b8::3.
ns7.markmonitor.com resolves to 149.112.161.2 and 2620:10a:80a9::2.