idating.com - dns.ninja

idating.com

DNSSEC⚠️ Not signed
A50.16.218.27🇺🇸 Amazon50.16.0.0/16 EC2 IAD prefix
PTRec2-50-16-218-27.compute-1.amazonaws.com
NSns1.digimedia.com ⭐
A23.21.242.88🇺🇸 Amazon23.20.0.0/15 EC2 IAD prefix
PTRec2-23-21-242-88.compute-1.amazonaws.com
NSns2.digimedia.com
A23.21.243.119🇺🇸 Amazon23.20.0.0/15 EC2 IAD prefix
PTRec2-23-21-243-119.compute-1.amazonaws.com
MX0.0.0.0 ⭐
TXTv=spf1 -all
SOAns1.digimedia.comdns@digimedia.com 2026-04-13 #1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1781536935

Same first word

idating.fr
idating.com
idating.cz
idating.biz
idating.org
idating.eu
idating.ru
idating.de
idating.com.au
idating.ch
idating.net
idating.xyz
idating.tv
idating.co.uk

Similar names

dignita.dk
daiting.ru
diginta.com
taiding.com.cn
inditag.com
giantid.com
gtindia.net
digitan.fr
dingtai.shop
dignita.org
digitan.com
diginat.com
dingtai.com.cn
tingdai.com
digitan.org
digitan.cloud
tgindia.com
taiding.com
digitan.ch
dingtai.cn
diginat.net
nadigit.com
daiting.com
dingtai.com.tw
diagnit.com
daiting.com.cn
digitan.de
dignita.com
daiting.ai
digitna.com
taiding.net
digiant.com
daiting.eu
datingi.com
daiting.dk
digiant.net
tgindia.in
daiting.info
dingtai.org
gtindia.com
digiant.com.tr
aditing.com
indiagt.com
ignitad.com
diganti.com

DNS History

15 records (4 active, 11 former)

20162017201820192020202120222023202420252026NSns1.digimedia.comns2.digimedia.comeric.ns.cloudflare.comolga.ns.cloudflare.comMX0.0.0.00.0.0.0mx.zoho.commx2.zoho.comA50.16.218.27104.31.80.117104.31.81.11723.21.179.13823.21.224.1502400:cb00:2048:1::681f:50752400:cb00:2048:1::681f:5175
○NSeric.ns.cloudflare.com2017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
●NSns1.digimedia.com2015-08-15 → 2026-06-15 · 5 obs
● 2015-08-15 08:23:28
● 2016-10-03 10:08:10
○ 2017-04-18 22:45:42
● 2026-02-18 22:15:30
● 2026-06-15 15:41:22
●NSns2.digimedia.com2015-08-15 → 2026-06-15 · 5 obs
● 2015-08-15 08:23:28
● 2016-10-03 10:08:10
○ 2017-04-18 22:45:42
● 2026-02-18 22:15:30
● 2026-06-15 15:41:22
○NSolga.ns.cloudflare.com2017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
●MX0.0.0.02015-08-15 → 2026-06-15 · 5 obs
● 2015-08-15 08:23:28
○ 2015-12-15 10:41:06
○ 2017-04-18 22:45:42
● 2026-02-18 22:15:30
● 2026-06-15 15:41:22
○MX0.0.0.02015-12-15 → 2016-10-03 · 5 obs
○ 2015-08-15 08:23:28
● 2015-12-15 10:41:06
● 2016-10-03 10:08:10
○ 2017-04-18 22:45:42
○ 2026-06-15 15:41:22
○MXmx.zoho.com2017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
○MXmx2.zoho.com2017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
○A104.31.80.1172017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
○A104.31.81.1172017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
○A23.21.179.1382015-08-15 → 2016-10-03 · 4 obs
● 2015-08-15 08:23:28
● 2016-10-03 10:08:10
○ 2017-04-18 22:45:42
○ 2026-06-15 15:41:22
○A23.21.224.1502015-08-15 → 2016-10-03 · 4 obs
● 2015-08-15 08:23:28
● 2016-10-03 10:08:10
○ 2017-04-18 22:45:42
○ 2026-06-15 15:41:22
○A2400:cb00:2048:1::681f:50752017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
○A2400:cb00:2048:1::681f:51752017-04-18 → 2017-04-18 · 4 obs
○ 2016-10-03 10:08:10
● 2017-04-18 22:45:42
○ 2026-02-18 22:15:30
○ 2026-06-15 15:41:22
●A50.16.218.272026-02-18 → 2026-06-15 · 3 obs
○ 2017-04-18 22:45:42
● 2026-02-18 22:15:30
● 2026-06-15 15:41:22

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
idating.comns1.digimedia.com, ns2.digimedia.com2 records

✅ Authoritative Response

Server:23.21.243.119

NS records: ns1.digimedia.com, ns2.digimedia.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for idating.com (unsigned zone)

⏱️ Timing

Total: 113ms | Queries: -

📄 Records

TypeCountSample Data
A150.16.218.27
NS2ns2.digimedia.com, ns1.digimedia.com
MX10.0.0.0 (pri: 1000)
TXT1v=spf1 -all
SOA1ns1.digimedia.com dns.digimedia.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.digimedia.com, ns2.digimedia.com)

Analysis

IP Addresses

idating.com points to a single IP number: 50.16.218.27.

Additional host names — son.com, eom.com, jamb.org.net and two others — share IP numbers with idating.com.

Name Servers

Two name servers handle the delegation for idating.com: ns1.digimedia.com and ns2.digimedia.com.

idating.com shares its name server setup with other domains, including computergames.net, graf.com, airside.com and two others.

There is at least partial name server overlap between idating.com and other domains — hotcar.com, santaluzia.com, ranges.com and two more among them.

These name servers are routinely deployed together with the name servers ns3.digimedia.com.

ns1.digimedia.com → 23.21.242.88 and ns2.digimedia.com → 23.21.243.119: one IP number per host name.

Mail Servers

idating.com has one mail server: 0.0.0.0.

idating.com shares the same mail server setup as other domains, including squredclub.org.net, ecosia.org.com, hungover.com and two others.