datingflash.com - robtex.com
datingflash.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@datingflash.com 2025-04-01 #1 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785011387 | ||||||
Same first word
datingflash.com |
Similar names
DNS History
22 records (3 active, 19 former)
●NSns1.atom.com2026-03-31 → 2026-07-25 · 3 obs
○ 2017-09-20 09:35:36
● 2026-03-31 15:27:44
● 2026-07-25 20:58:02
● 2026-03-31 15:27:44
● 2026-07-25 20:58:02
○NSns1.namebrightdns.com2015-07-09 → 2017-09-20 · 8 obs
● 2015-07-09 05:54:18
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
● 2017-09-20 09:35:36
○ 2026-03-31 15:27:44
○ 2026-07-25 20:58:02
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
● 2017-09-20 09:35:36
○ 2026-03-31 15:27:44
○ 2026-07-25 20:58:02
●NSns2.atom.com2026-03-31 → 2026-07-25 · 3 obs
○ 2017-09-20 09:35:36
● 2026-03-31 15:27:44
● 2026-07-25 20:58:02
● 2026-03-31 15:27:44
● 2026-07-25 20:58:02
○NSns2.namebrightdns.com2015-07-09 → 2017-09-20 · 8 obs
● 2015-07-09 05:54:18
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
● 2017-09-20 09:35:36
○ 2026-03-31 15:27:44
○ 2026-07-25 20:58:02
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
● 2017-09-20 09:35:36
○ 2026-03-31 15:27:44
○ 2026-07-25 20:58:02
○NSnsg1.namebrightdns.com2016-02-02 → 2016-02-02 · 4 obs
○ 2015-11-10 12:51:34
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
○NSnsg2.namebrightdns.com2016-02-02 → 2016-02-02 · 4 obs
○ 2015-11-10 12:51:34
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
○NSnst1.namebrightdns.com2016-12-04 → 2016-12-04 · 4 obs
○ 2016-04-24 06:39:38
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○NSnst2.namebrightdns.com2016-12-04 → 2016-12-04 · 4 obs
○ 2016-04-24 06:39:38
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○MXanmail.namebrightmail.com2015-07-09 → 2015-07-09 · 3 obs
● 2015-07-09 05:54:18
○ 2015-11-10 12:51:34
○ 2026-07-25 20:58:02
○ 2015-11-10 12:51:34
○ 2026-07-25 20:58:02
○A107.23.95.2352015-07-09 → 2015-07-09 · 3 obs
● 2015-07-09 05:54:18
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
●A52.20.84.622026-03-31 → 2026-07-25 · 3 obs
○ 2017-09-20 09:35:36
● 2026-03-31 15:27:44
● 2026-07-25 20:58:02
● 2026-03-31 15:27:44
● 2026-07-25 20:58:02
○A52.200.243.1232016-04-24 → 2016-04-24 · 4 obs
○ 2016-02-02 08:23:26
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
○ 2026-07-25 20:58:02
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
○ 2026-07-25 20:58:02
○A54.152.144.2432016-04-24 → 2016-04-24 · 4 obs
○ 2016-02-02 08:23:26
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
○ 2026-07-25 20:58:02
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
○ 2026-07-25 20:58:02
○A54.174.31.2542015-11-10 → 2015-11-10 · 4 obs
○ 2015-07-09 05:54:18
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
○ 2026-07-25 20:58:02
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
○ 2026-07-25 20:58:02
○A54.208.74.2152015-11-10 → 2015-11-10 · 4 obs
○ 2015-07-09 05:54:18
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
○ 2026-07-25 20:58:02
● 2015-11-10 12:51:34
○ 2016-02-02 08:23:26
○ 2026-07-25 20:58:02
○A54.209.90.812016-02-02 → 2016-02-02 · 4 obs
○ 2015-11-10 12:51:34
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
○A54.84.74.522015-07-09 → 2015-07-09 · 3 obs
● 2015-07-09 05:54:18
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○A54.84.80.1732016-12-04 → 2016-12-04 · 4 obs
○ 2016-04-24 06:39:38
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○A54.85.54.292016-02-02 → 2016-02-02 · 4 obs
○ 2015-11-10 12:51:34
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
● 2016-02-02 08:23:26
○ 2016-04-24 06:39:38
○ 2026-07-25 20:58:02
○A54.88.107.1402016-12-04 → 2016-12-04 · 4 obs
○ 2016-04-24 06:39:38
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
● 2016-12-04 10:56:30
○ 2017-09-20 09:35:36
○ 2026-07-25 20:58:02
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-07-09 → 2016-04-24 · 4 obs
● 2015-07-09 05:54:18
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
○ 2026-07-25 20:58:02
● 2016-04-24 06:39:38
○ 2016-12-04 10:56:30
○ 2026-07-25 20:58:02
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2016-12-04 → 2017-09-20 · 5 obs
○ 2016-04-24 06:39:38
● 2016-12-04 10:56:30
● 2017-09-20 09:35:36
○ 2026-03-31 15:27:44
○ 2026-07-25 20:58:02
● 2016-12-04 10:56:30
● 2017-09-20 09:35:36
○ 2026-03-31 15:27:44
○ 2026-07-25 20:58:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net... | - |
| datingflash.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for datingflash.com (unsigned zone)
⏱️ Timing
Total: 3242ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.atom.com hostmaster.datingflash.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
datingflash.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with opticarc.com, hickly.com and rampbase.com, also share IP numbers with datingflash.com.
Name Servers
Two name servers handle the delegation for datingflash.com: ns1.atom.com and ns2.atom.com.
datingflash.com shares its NS records with other domains, for example casegym.com, gamesfi.com, risegrace.com and two others.
At least some of datingflash.com's name servers are shared with other domains, for example trixair.com, fayq.com, topfasad.com and two more.
These name servers tend to be deployed in combination with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn and verification-8uneycqadhrltns2lewzss.ns101.verify.hn.
Each of ns1.atom.com and ns2.atom.com has one IP address: ns1.atom.com uses 44.219.81.145 and ns2.atom.com uses 50.19.240.86.