amsignalling.com - dns.ninja

`amsignalling.com`

DNSSEC	⚠️ Not signed
NS	`dns1.cscdns.net` ⭐
		A	2610:a1:1022::100^{🇺🇸 MAINT-ID-120082610:a1:1022::/48 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
		A	156.154.130.100^{🇺🇸 MAINT-ID-12008156.154.130.0/24 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`ns5.bac.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`g.ns-bac.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
NS	`dns2.cscdns.net`
		A	2610:a1:1023::100^{🇺🇸 MAINT-ID-120082610:a1:1023::/48 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
		A	156.154.131.100^{🇺🇸 MAINT-ID-12008156.154.131.0/24 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`ns9.bac.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
			PTR	`h.ns-bac.org`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2018-03-06 #12

`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=1786537134

Same first word

amsignalling.com

DNS History

10 records (2 active, 8 former)

●NSdns1.cscdns.net2018-06-13 → 2026-08-12 · 3 obs

○ 2017-01-14 10:51:16
● 2018-06-13 15:00:32
● 2026-08-12 12:33:44

●NSdns2.cscdns.net2018-06-13 → 2026-08-12 · 3 obs

○ 2017-01-14 10:51:16
● 2018-06-13 15:00:32
● 2026-08-12 12:33:44

○NSns.webfusion.co.uk2015-06-23 → 2017-01-14 · 4 obs

● 2015-06-23 23:19:04
● 2017-01-14 10:51:16
○ 2018-06-13 15:00:32
○ 2026-08-12 12:33:44

○NSns2.webfusion.co.uk2015-06-23 → 2017-01-14 · 4 obs

● 2015-06-23 23:19:04
● 2017-01-14 10:51:16
○ 2018-06-13 15:00:32
○ 2026-08-12 12:33:44

○MXamsignalling-com.mail.protection.outlook.com2016-05-04 → 2018-06-13 · 5 obs

○ 2016-02-23 03:22:10
● 2016-05-04 07:34:20
● 2018-06-13 15:00:32
○ 2026-03-12 22:49:46
○ 2026-08-12 12:33:44

○MXmx0.123-reg.co.uk2015-06-23 → 2016-02-23 · 4 obs

● 2015-06-23 23:19:04
● 2016-02-23 03:22:10
○ 2016-05-04 07:34:20
○ 2026-08-12 12:33:44

○MXmx1.123-reg.co.uk2015-06-23 → 2016-02-23 · 4 obs

● 2015-06-23 23:19:04
● 2016-02-23 03:22:10
○ 2016-05-04 07:34:20
○ 2026-08-12 12:33:44

○A137.117.84.542018-06-13 → 2018-06-13 · 4 obs

○ 2017-01-14 10:51:16
● 2018-06-13 15:00:32
○ 2026-03-12 22:49:46
○ 2026-08-12 12:33:44

○A94.136.40.1802015-06-23 → 2015-11-06 · 4 obs

● 2015-06-23 23:19:04
● 2015-11-06 22:33:16
○ 2016-02-23 03:22:10
○ 2026-08-12 12:33:44

○A94.136.40.822016-02-23 → 2017-01-14 · 5 obs

○ 2015-11-06 22:33:16
● 2016-02-23 03:22:10
● 2017-01-14 10:51:16
○ 2018-06-13 15:00:32
○ 2026-08-12 12:33:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net...	-
amsignalling.com	dns1.cscdns.net, dns2.cscdns.net	-

✅ Authoritative Response

Server:156.154.131.100

NS records: dns1.cscdns.net, dns2.cscdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for amsignalling.com (unsigned zone)

⏱️ Timing

Total: 1283ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.cscdns.net, dns2.cscdns.net`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

Analysis

Name Servers

amsignalling.com is delegated to two name servers: dns1.cscdns.net and dns2.cscdns.net.

amsignalling.com has the same name server delegation as a number of other domains, such as zalesdiamondstore.com, mikebloombergphilanthropy.nyc, thisoldhousekids.com and two more.

amsignalling.com has a partial name server overlap with other domains — among them mbnasurvey.com and merill-lynch.us.

It is common to see these name servers used together with name servers ns101.bac.com and ns102.bac.com.

dns1.cscdns.net and dns2.cscdns.net each resolve to two IP addresses: dns1.cscdns.net points to 156.154.130.100 and 2610:a1:1022::100, while dns2.cscdns.net points to 156.154.131.100 and 2610:a1:1023::100.