`cardservicing.com`

DNSSEC	⚠️ Not signed
NS	`ns-246.awsdns-30.com` ⭐
		A	2600:9000:5300:f600::1^{🇺🇸 Amazon}
			PTR	`ns-246.awsdns-30.com`
		A	205.251.192.246^{🇺🇸 Amazon}
			PTR	`ns-246.awsdns-30.com`
NS	`ns-1465.awsdns-55.org`
		A	2600:9000:5305:b900::1^{🇺🇸 Amazon}
			PTR	`ns-1465.awsdns-55.org`
		A	205.251.197.185^{🇺🇸 Amazon}
			PTR	`ns-1465.awsdns-55.org`
NS	`ns-1672.awsdns-17.co.uk`
		A	2600:9000:5306:8800::1^{🇺🇸 Amazon}
			PTR	`ns-1672.awsdns-17.co.uk`
		A	205.251.198.136^{🇺🇸 Amazon}
			PTR	`ns-1672.awsdns-17.co.uk`
NS	`ns-516.awsdns-00.net`
		A	2600:9000:5302:400::1^{🇺🇸 Amazon}
			PTR	`ns-516.awsdns-00.net`
		A	205.251.194.4^{🇺🇸 Amazon}
			PTR	`ns-516.awsdns-00.net`
MX	`cardservicing-com.mail.protection.outlook.com` ⭐
TXT	`MS=ms40756952`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns-246.awsdns-30.com`awsdns-hostmaster@amazon.com serial=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.net`nstld@verisign-grs.com serial=1771291435

DNS History

9 records (5 active, 4 former)

●NSns-1465.awsdns-55.org2026-02-22 → 2026-02-22 · 2 obs

○ 2017-05-14 19:26:36
● 2026-02-22 18:04:56

●NSns-1672.awsdns-17.co.uk2026-02-22 → 2026-02-22 · 2 obs

○ 2017-05-14 19:26:36
● 2026-02-22 18:04:56

●NSns-246.awsdns-30.com2026-02-22 → 2026-02-22 · 2 obs

○ 2017-05-14 19:26:36
● 2026-02-22 18:04:56

●NSns-516.awsdns-00.net2026-02-22 → 2026-02-22 · 2 obs

○ 2017-05-14 19:26:36
● 2026-02-22 18:04:56

○NSns05.jpmorganchase.com2015-07-26 → 2017-05-14 · 3 obs

● 2015-07-26 09:02:36
● 2017-05-14 19:26:36
○ 2026-02-22 18:04:56

○NSns06.jpmorganchase.com2015-07-26 → 2017-05-14 · 3 obs

● 2015-07-26 09:02:36
● 2017-05-14 19:26:36
○ 2026-02-22 18:04:56

○NSns1.jpmorganchase.com2015-07-26 → 2017-05-14 · 3 obs

● 2015-07-26 09:02:36
● 2017-05-14 19:26:36
○ 2026-02-22 18:04:56

○NSns2.jpmorganchase.com2015-07-26 → 2017-05-14 · 3 obs

● 2015-07-26 09:02:36
● 2017-05-14 19:26:36
○ 2026-02-22 18:04:56

●MXcardservicing-com.mail.protection.outlook.com2026-02-22 → 2026-02-22 · 1 obs

● 2026-02-22 18:04:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cardservicing.com	ns-246.awsdns-30.com, ns-516.awsdns-00.net, ns-1672.awsdns-17.co.uk, ns-1465.awsdns-55.org	-

✅ Authoritative Response

Server: 205.251.194.4

NS records: ns-246.awsdns-30.com, ns-516.awsdns-00.net, ns-1672.awsdns-17.co.uk, ns-1465.awsdns-55.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cardservicing.com (unsigned zone)

⏱️ Timing

Total: 105ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1465.awsdns-55.org, ns-1672.awsdns-17.co.uk...`
MX	1	`cardservicing-com.mail.protection.outloo`
TXT	2	`MS=ms40756952, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns-246.awsdns-30.com awsdns-hostmaster.a`

AI analysis

cardservicing.com delegates to four name servers: ns-246.awsdns-30.com, ns-516.awsdns-00.net, ns-1465.awsdns-55.org and ns-1672.awsdns-17.co.uk.

cardservicing.com at least partially shares name servers with other domains, for instance laylagrayce.com, cineticket.com.mx, peko.vn, ssbme.org and tvwebmaanaim.com.br.

These name servers are commonly used with the following: ns-1956.awsdns-52.co.uk, ns-668.awsdns-19.net, ns-1842.awsdns-38.co.uk and ns-524.awsdns-01.net.

Host names with two IP numbers: ns-246.awsdns-30.com points to 2600:9000:5300:f600::1 and 205.251.192.246; ns-516.awsdns-00.net points to 2600:9000:5302:400::1 and 205.251.194.4; ns-1465.awsdns-55.org points to 2600:9000:5305:b900::1 and 205.251.197.185; ns-1672.awsdns-17.co.uk points to 2600:9000:5306:8800::1 and 205.251.198.136.

cardservicing.com is handled by a single mail server, cardservicing-com.mail.protection.outlook.com.

cardservicing.com - robtex.com