digiday.com - dns.ninja

`digiday.com`

DNSSEC	⚠️ Not signed
A	192.0.66.72^{🇺🇸 Automattic192.0.66.0/24 Route Object}
NS	`ns-1946.awsdns-51.co.uk` ⭐
		A	2600:9000:5307:9a00::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1946.awsdns-51.co.uk`
		A	205.251.199.154^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1946.awsdns-51.co.uk`
NS	`ns-1350.awsdns-40.org`
		A	2600:9000:5305:4600::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1350.awsdns-40.org`
		A	205.251.197.70^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1350.awsdns-40.org`
NS	`ns-499.awsdns-62.com`
		A	2600:9000:5301:f300::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-499.awsdns-62.com`
		A	205.251.193.243^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-499.awsdns-62.com`
NS	`ns-650.awsdns-17.net`
		A	2600:9000:5302:8a00::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-650.awsdns-17.net`
		A	205.251.194.138^{🇺🇸 Amazon205.251.194.0/24 prefix}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`_globalsign-domain-verification=Y1ChKN5EECy1Kw7F_iAFAiUJj(0x736558)TTVSj2FbRzOgy2`
TXT	`_globalsign-domain-verification=fsrfW7Xky97daWCU-mDTGZh-Fqns_6wvS3p-DBPbF_`
TXT	`apple-domain-verification=cXHPYDU1Uxw16lTR7koE4DMl34glorNa1Dgekj6Nenk`
TXT	`asv=1099825f580a90719aca4e43144151f5`
TXT	`google-site-verification=gIUHiWVgTvXUHl8stKtEMCAK9ezACe-WpeZgq9DtTgw`
TXT	`v=spf1 include:aspmx.sailthru.com include:_spf.google.com include:spf.mandril...`
SOA	`ns-1946.awsdns-51.co.uk`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=1783891397

rank #3349 globally
rank #1728 in the tld
WOT: SAFE (81/100)
📈 Tranco rank: #14,378

Subdomains

ox-i.digiday.com

www.digiday.com

Same first word

digiday.ru

digiday.leadpages.co

digiday.co

digiday.mobi

digiday.jp

digiday.nl

digiday.org

digiday.us

digiday.de

digiday.com

digiday.tv

digiday.net

DNS History

22 records (10 active, 12 former)

●NSns-1350.awsdns-40.org2026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

○NSns-1520.awsdns-62.org2015-08-31 → 2019-01-16 · 4 obs

● 2015-08-31 22:30:22
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○NSns-1610.awsdns-09.co.uk2015-08-31 → 2019-01-16 · 4 obs

● 2015-08-31 22:30:22
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○NSns-173.awsdns-21.com2015-08-31 → 2019-01-16 · 4 obs

● 2015-08-31 22:30:22
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

●NSns-1946.awsdns-51.co.uk2026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

●NSns-499.awsdns-62.com2026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

●NSns-650.awsdns-17.net2026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

○NSns-884.awsdns-46.net2015-08-31 → 2019-01-16 · 4 obs

● 2015-08-31 22:30:22
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

●MXalt1.aspmx.l.google.com2015-08-31 → 2026-07-12 · 2 obs

● 2015-08-31 22:30:22
● 2026-07-12 21:47:02

●MXalt2.aspmx.l.google.com2015-08-31 → 2026-07-12 · 2 obs

● 2015-08-31 22:30:22
● 2026-07-12 21:47:02

●MXalt3.aspmx.l.google.com2026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

●MXalt4.aspmx.l.google.com2026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

●MXaspmx.l.google.com2015-08-31 → 2026-07-12 · 2 obs

● 2015-08-31 22:30:22
● 2026-07-12 21:47:02

○MXaspmx2.googlemail.com2015-08-31 → 2019-01-16 · 4 obs

● 2015-08-31 22:30:22
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○MXaspmx3.googlemail.com2015-08-31 → 2019-01-16 · 4 obs

● 2015-08-31 22:30:22
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○A151.101.130.492019-01-16 → 2019-01-16 · 4 obs

○ 2017-02-12 18:10:52
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○A151.101.194.492019-01-16 → 2019-01-16 · 4 obs

○ 2017-02-12 18:10:52
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○A151.101.2.492019-01-16 → 2019-01-16 · 4 obs

○ 2017-02-12 18:10:52
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

○A151.101.66.492019-01-16 → 2019-01-16 · 4 obs

○ 2017-02-12 18:10:52
● 2019-01-16 20:16:04
○ 2026-02-18 23:10:30
○ 2026-07-12 21:47:02

●A192.0.66.722026-02-18 → 2026-07-12 · 3 obs

○ 2019-01-16 20:16:04
● 2026-02-18 23:10:30
● 2026-07-12 21:47:02

○A198.61.251.612015-08-31 → 2017-02-12 · 4 obs

● 2015-08-31 22:30:22
● 2017-02-12 18:10:52
○ 2019-01-16 20:16:04
○ 2026-07-12 21:47:02

○A2001:4801:7901:0:aff8:a2d8:0:4aa2015-08-31 → 2017-02-12 · 4 obs

● 2015-08-31 22:30:22
● 2017-02-12 18:10:52
○ 2019-01-16 20:16:04
○ 2026-07-12 21:47:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
digiday.com	ns-650.awsdns-17.net, ns-499.awsdns-62.com, ns-1946.awsdns-51.co.uk, ns-1350.awsdns-40.org	2 records

✅ Authoritative Response

Server:205.251.197.70

NS records: ns-650.awsdns-17.net, ns-499.awsdns-62.com, ns-1946.awsdns-51.co.uk, ns-1350.awsdns-40.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for digiday.com (unsigned zone)

⏱️ Timing

Total: 955ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`192.0.66.72`
NS	4	`ns-1350.awsdns-40.org, ns-1946.awsdns-51.co.uk...`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	6	`_globalsign-domain-verification=Y1ChKN5E, _globalsign-domain-verification=fsrfW7Xk...`
SOA	1	`ns-1946.awsdns-51.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-499.awsdns-62.com, ns-499.awsdns-62.com)

Analysis

Hierarchy

The parent domain of ox-i.digiday.com and www.digiday.com is digiday.com.

IP Addresses

digiday.com directs to one IP number, which is 192.0.66.72.

Among the host names that share IP numbers with digiday.com are www.blogsicilia.it, siciliafan.it, www.digidaymedia.com and two others.

Name Servers

The domain digiday.com is delegated to these four name servers: ns-499.awsdns-62.com, ns-650.awsdns-17.net, ns-1350.awsdns-40.org and ns-1946.awsdns-51.co.uk.

The name servers of digiday.com overlap at least partially with those of other domains — among them d1mlqfxu823sjw.cloudfront.net, be2webo.co.kr, f36f4d549d6d67668214bffdb381b5b1df8980e64426098127cc9efc35b2ef0.link and two more.

Each of the four hosts ns-499.awsdns-62.com, ns-650.awsdns-17.net, ns-1350.awsdns-40.org and ns-1946.awsdns-51.co.uk has two IP addresses. ns-499.awsdns-62.com points to 205.251.193.243 and 2600:9000:5301:f300::1. ns-650.awsdns-17.net points to 205.251.194.138 and 2600:9000:5302:8a00::1. ns-1350.awsdns-40.org points to 205.251.197.70 and 2600:9000:5305:4600::1. ns-1946.awsdns-51.co.uk points to 205.251.199.154 and 2600:9000:5307:9a00::1.

Mail Servers

digiday.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

digiday.com shares at least some of its mail servers with other domains — for example ns500754.ns500671.ns500742.ns500671.ns500671.ns500742.ns500688.ns500704.ns500291.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500765.ns500734.ns500693.ns500693.ns500734.ns500734.ns500588.ns500683.ns500699.ns500632.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500759.ns500759.ns500758.ns500758.ns500735.ns500698.ns500735.ns500735.ns500708.ns500576.ns500708.ns500652.ns500652.trackreceptor.com and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.