`flickerstage.com`

DNSSEC	⚠️ Not signed
A	149.30.196.250^{🇺🇸 SONDERCLOUD-1149.30.196.0/24 Proxy-registered route object}
NS	`ns1.julydns.com` ⭐
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.julydns.com`
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ns1.julydns.com`master@jmdns.com serial=1759687246

`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.net`nstld@verisign-grs.com serial=1778527971

Previously MX for

www.flickerstage.com

Subdomains

www.flickerstage.com

Same first word

flickerstage.com

DNS History

22 records (3 active, 19 former)

●NSns1.julydns.com2026-03-09 → 2026-05-11 · 3 obs

○ 2019-12-30 08:01:40
● 2026-03-09 16:49:56
● 2026-05-11 19:37:10

○NSns1.m42.siteground.biz2019-12-30 → 2019-12-30 · 4 obs

○ 2017-02-08 16:46:48
● 2019-12-30 08:01:40
○ 2026-03-09 16:49:56
○ 2026-05-11 19:37:10

●NSns2.julydns.com2026-03-09 → 2026-05-11 · 3 obs

○ 2019-12-30 08:01:40
● 2026-03-09 16:49:56
● 2026-05-11 19:37:10

○NSns2.m42.siteground.biz2019-12-30 → 2019-12-30 · 4 obs

○ 2017-02-08 16:46:48
● 2019-12-30 08:01:40
○ 2026-03-09 16:49:56
○ 2026-05-11 19:37:10

○NSns6251.hostgator.com2017-02-08 → 2017-02-08 · 4 obs

○ 2016-06-29 00:24:48
● 2017-02-08 16:46:48
○ 2019-12-30 08:01:40
○ 2026-05-11 19:37:10

○NSns6252.hostgator.com2017-02-08 → 2017-02-08 · 4 obs

○ 2016-06-29 00:24:48
● 2017-02-08 16:46:48
○ 2019-12-30 08:01:40
○ 2026-05-11 19:37:10

○NSns73.domaincontrol.com2015-08-18 → 2016-06-29 · 4 obs

● 2015-08-18 23:02:10
● 2016-06-29 00:24:48
○ 2017-02-08 16:46:48
○ 2026-05-11 19:37:10

○NSns74.domaincontrol.com2015-08-18 → 2016-06-29 · 4 obs

● 2015-08-18 23:02:10
● 2016-06-29 00:24:48
○ 2017-02-08 16:46:48
○ 2026-05-11 19:37:10

○MXalt1.aspmx.l.google.com2015-08-18 → 2015-08-18 · 3 obs

● 2015-08-18 23:02:10
○ 2015-12-04 01:54:12
○ 2026-05-11 19:37:10

○MXalt2.aspmx.l.google.com2015-08-18 → 2015-08-18 · 3 obs

● 2015-08-18 23:02:10
○ 2015-12-04 01:54:12
○ 2026-05-11 19:37:10

○MXaspmx.l.google.com2015-08-18 → 2015-08-18 · 3 obs

● 2015-08-18 23:02:10
○ 2015-12-04 01:54:12
○ 2026-05-11 19:37:10

○MXaspmx2.googlemail.com2015-08-18 → 2015-08-18 · 3 obs

● 2015-08-18 23:02:10
○ 2015-12-04 01:54:12
○ 2026-05-11 19:37:10

○MXaspmx3.googlemail.com2015-08-18 → 2015-08-18 · 3 obs

● 2015-08-18 23:02:10
○ 2015-12-04 01:54:12
○ 2026-05-11 19:37:10

○MXflickerstage-com.mail.protection.outlook.com2015-12-04 → 2016-06-29 · 5 obs

○ 2015-08-18 23:02:10
● 2015-12-04 01:54:12
● 2016-06-29 00:24:48
○ 2017-02-08 16:46:48
○ 2026-05-11 19:37:10

○MXmail.flickerstage.com2017-02-08 → 2017-02-08 · 4 obs

○ 2016-06-29 00:24:48
● 2017-02-08 16:46:48
○ 2019-12-30 08:01:40
○ 2026-05-11 19:37:10

○MXmx10.mailspamprotection.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-02-08 16:46:48
● 2019-12-30 08:01:40
○ 2026-03-09 16:49:56
○ 2026-05-11 19:37:10

○MXmx20.mailspamprotection.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-02-08 16:46:48
● 2019-12-30 08:01:40
○ 2026-03-09 16:49:56
○ 2026-05-11 19:37:10

○MXmx30.mailspamprotection.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-02-08 16:46:48
● 2019-12-30 08:01:40
○ 2026-03-09 16:49:56
○ 2026-05-11 19:37:10

●A149.30.196.2502026-03-09 → 2026-05-11 · 3 obs

○ 2019-12-30 08:01:40
● 2026-03-09 16:49:56
● 2026-05-11 19:37:10

○A185.56.85.2442019-12-30 → 2019-12-30 · 4 obs

○ 2017-02-08 16:46:48
● 2019-12-30 08:01:40
○ 2026-03-09 16:49:56
○ 2026-05-11 19:37:10

○A192.254.187.1562017-02-08 → 2017-02-08 · 4 obs

○ 2016-06-29 00:24:48
● 2017-02-08 16:46:48
○ 2019-12-30 08:01:40
○ 2026-05-11 19:37:10

○A65.39.205.542015-08-18 → 2016-06-29 · 4 obs

● 2015-08-18 23:02:10
● 2016-06-29 00:24:48
○ 2017-02-08 16:46:48
○ 2026-05-11 19:37:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
flickerstage.com	ns1.julydns.com, ns2.julydns.com	2 records

✅ Authoritative Response

Server:162.159.48.223

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flickerstage.com (unsigned zone)

⏱️ Timing

Total: 312ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`149.30.196.250`
NS	2	`ns1.julydns.com, ns2.julydns.com`
SOA	1	`ns1.julydns.com master.jmdns.com`

📌 Glue Records Collected

Total: 2

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

Analysis

Hierarchy

The parent of www.flickerstage.com is flickerstage.com.

IP Addresses

flickerstage.com points to a single IP number: 149.30.196.250.

Other host names, for example shunchangcm.com, www.flickerstage.com, zjshenghan.com and 6q3.cn share IP numbers with flickerstage.com.

Name Servers

flickerstage.com is delegated to two name servers: ns1.julydns.com and ns2.julydns.com.

flickerstage.com uses the same name server setup as other domains, for instance cbn10099.com, yynantian.com, 360meiye.com, roshnsaudileague.live and zhensen168.com.

flickerstage.com shares name servers with other domains at least partially, for instance dwsdn.cn, hxsa.net, puyr999.com, communicationresponsable.com and officemavens.com.

these name servers are commonly used together with ns1.judns.com and ns2.judns.com.

Host names with a single IP number:

ns1.julydns.com points to 162.159.48.223.

ns2.julydns.com points to 162.159.48.223.

Host names pointing to 162.159.48.223: ns1.julydns.com and ns2.julydns.com.

flickerstage.com - robtex.com