`inputs3.glic.splunkcloud.com`

DNSSEC	⚠️ Not signed
A	34.208.26.151^{🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix}
		PTR	`ec2-34-208-26-151.us-west-2.compute.amazonaws.com`
A	34.223.161.82^{🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix}
A	35.162.187.75^{🇺🇸 Amazon35.160.0.0/13 EC2 PDX prefix}
A	52.26.76.157^{🇺🇸 Amazon52.24.0.0/14 EC2 PDX prefix}
A	52.34.188.198^{🇺🇸 Amazon52.32.0.0/14 EC2 PDX prefix}
A	52.88.141.192^{🇺🇸 Amazon52.88.0.0/15 EC2 PDX Prefix}
A	54.212.54.141^{🇺🇸 Amazon54.212.0.0/16 EC2 PDX prefix}

`glic.splunkcloud.com`

	DNSSEC	⚠️ Not signed
	A	44.231.26.58^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
	A	44.240.166.51^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
	A	54.200.95.137^{🇺🇸 Amazon54.200.0.0/15 EC2 PDX prefix}
	NS	`ns-1549.awsdns-01.co.uk` ⭐
	NS	`ns-5-3-1.splunkdns.net`
	NS	`ns-5-3-2.splunkdns.net`
	NS	`ns-5-3-3.splunkdns.net`
	NS	`ns-5-3-4.splunkdns.net`
	NS	`ns-5-3-5.splunkdns.net`
	NS	`ns-5-3-6.splunkdns.net`
	NS	`ns-5-3-7.splunkdns.net`
	NS	`ns-5-3-8.splunkdns.net`
	SOA	`ns-1549.awsdns-01.co.uk`awsdns-hostmaster@amazon.com serial=1

⚠️ On DNS blocklist: pro.plus, ultimate
⚠️ On DNS blocklist: pro.plus, ultimate

DNS History

7 records (7 active, 0 former)

●A34.208.26.1512026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

●A34.223.161.822026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

●A35.162.187.752026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

●A52.26.76.1572026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

●A52.34.188.1982026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

●A52.88.141.1922026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

●A54.212.54.1412026-02-18 → 2026-04-24 · 2 obs

● 2026-02-18 08:11:54
● 2026-04-24 02:58:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net...	-
splunkcloud.com	ns-4-2-1.splunkdns.net, ns-4-2-2.splunkdns.net, ns-4-2-3.splunkdns.net, ns-4-2-4.splunkdns.net...	-
glic.splunkcloud.com	ns-5-3-1.splunkdns.net, ns-5-3-2.splunkdns.net, ns-5-3-3.splunkdns.net, ns-5-3-4.splunkdns.net...	-

✅ Authoritative Response

Server:205.251.193.41

NS records: ns-5-3-1.splunkdns.net, ns-5-3-2.splunkdns.net, ns-5-3-3.splunkdns.net, ns-5-3-4.splunkdns.net, ns-5-3-5.splunkdns.net, ns-5-3-6.splunkdns.net, ns-5-3-7.splunkdns.net, ns-5-3-8.splunkdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for splunkcloud.com (unsigned zone)

⏱️ Timing

Total: 759ms | Queries: -

📄 Records

Type	Count	Sample Data
A	7	`35.162.187.75, 34.208.26.151...`

Analysis

IP Addresses

inputs3.glic.splunkcloud.com points to seven IP numbers: 34.208.26.151, 34.223.161.82, 35.162.187.75, 52.26.76.157, 52.34.188.198, 52.88.141.192 and 54.212.54.141.

Other host names, for example inputs9.glic.splunkcloud.com, inputs12.glic.splunkcloud.com, inputs15.glic.splunkcloud.com and inputs6.glic.splunkcloud.com share IP numbers with inputs3.glic.splunkcloud.com.

inputs3.glic.splunkcloud.com - robtex.com