fashionalerts.com - robtex.com
fashionalerts.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 | ||||||
| SOA | ns1.atom.comhostmaster@fashionalerts.com 2026-03-09 #3 | ||||||
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=1785427927 | ||||||
Same first word
fashionalerts.com |
DNS History
23 records (3 active, 20 former)
○NSmyns1.fabulous.com2020-01-10 → 2020-01-10 · 3 obs
● 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○NSmyns2.fabulous.com2020-01-10 → 2020-01-10 · 3 obs
● 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○NSns1.dnsowl.com2026-07-30 → 2026-07-30 · 1 obs
○NSns1.fabulous.com2008-03-18 → 2017-02-20 · 4 obs
● 2017-02-20 11:41:24
○ 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○NSns2.dnsowl.com2026-07-30 → 2026-07-30 · 1 obs
○NSns2.fabulous.com2008-03-18 → 2017-02-20 · 4 obs
● 2017-02-20 11:41:24
○ 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○NSns3.dnsowl.com2026-07-30 → 2026-07-30 · 1 obs
○MXmail.b-io.co2015-07-05 → 2017-02-20 · 5 obs
● 2015-07-05 12:12:18
● 2017-02-20 11:41:24
○ 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○MXpostbox.fabulous.com2008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 12:12:18
○ 2026-07-30 16:36:04
○A107.161.23.2042026-07-30 → 2026-07-30 · 1 obs
○A185.53.177.312020-01-10 → 2020-01-10 · 3 obs
● 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○A198.251.81.302026-07-30 → 2026-07-30 · 1 obs
○A208.48.81.1332015-07-05 → 2015-12-09 · 5 obs
● 2015-07-05 12:12:18
● 2015-12-09 08:41:44
○ 2016-03-18 16:34:10
○ 2026-07-30 16:36:04
○A208.48.81.1342015-07-05 → 2015-12-09 · 5 obs
● 2015-07-05 12:12:18
● 2015-12-09 08:41:44
○ 2016-03-18 16:34:10
○ 2026-07-30 16:36:04
○A208.48.81.1792015-07-05 → 2015-10-06 · 5 obs
● 2015-07-05 12:12:18
● 2015-10-06 14:20:18
○ 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
○A209.141.38.712026-07-30 → 2026-07-30 · 1 obs
○A216.34.131.1352008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 12:12:18
○ 2026-07-30 16:36:04
●A52.20.84.622026-07-30 → 2026-07-30 · 2 obs
● 2026-07-30 16:36:04
○A64.15.205.1002015-07-05 → 2015-12-09 · 5 obs
● 2015-07-05 12:12:18
● 2015-12-09 08:41:44
○ 2016-03-18 16:34:10
○ 2026-07-30 16:36:04
○A64.15.205.1012015-07-05 → 2015-12-09 · 5 obs
● 2015-07-05 12:12:18
● 2015-12-09 08:41:44
○ 2016-03-18 16:34:10
○ 2026-07-30 16:36:04
○A98.124.245.242016-03-18 → 2017-02-20 · 5 obs
● 2016-03-18 16:34:10
● 2017-02-20 11:41:24
○ 2020-01-10 03:36:26
○ 2026-07-30 16:36:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| fashionalerts.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 fashionalerts.com (unsigned zone)
⏱️ Timing
Total: 3038ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.fashionalerts.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
fashionalerts.com points to a single IP number: 52.20.84.62.
Additional host names — locyn.com, bearddog.com, dink.com and two others — share IP numbers with fashionalerts.com.
Name Servers
DNS delegation for fashionalerts.com points to two name servers: ns1.atom.com and ns2.atom.com.
fashionalerts.com shares its name server setup with other domains, including pepperjobs.com, pureart.org, bingoforacause.com and two others.
The name servers for fashionalerts.com overlap at least in part with those of other domains, including propertyinsurancehouston.com and nimbustime.com.
These name servers commonly co-occur with the name servers ns1.sedoparking.com, ns2.sedoparking.com, ns3.afternic.com and ns4.afternic.com.
Both ns1.atom.com and ns2.atom.com have a single IP address each — ns1.atom.com resolves to 44.219.81.145 while ns2.atom.com resolves to 50.19.240.86.