weddingtask.com - dns.ninja

`weddingtask.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.afternic.com` ⭐
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com`
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`verification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net 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=1782865206

Same first word

weddingtask.com

Similar names

weddingkast.com

DNS History

25 records (5 active, 20 former)

○NSns07.domaincontrol.com2008-03-14 → 2008-03-14 · 3 obs

● 2008-03-14 15:26:32
○ 2015-06-25 10:30:58
○ 2026-07-01 00:31:22

○NSns08.domaincontrol.com2008-03-14 → 2008-03-14 · 3 obs

● 2008-03-14 15:26:32
○ 2015-06-25 10:30:58
○ 2026-07-01 00:31:22

●NSns1.afternic.com2026-03-21 → 2026-07-01 · 3 obs

○ 2018-11-10 20:03:36
● 2026-03-21 01:46:18
● 2026-07-01 00:31:22

○NSns1.namebrightdns.com2015-06-25 → 2018-11-10 · 8 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
● 2016-02-03 17:48:14
○ 2016-04-23 17:02:24
● 2017-02-07 21:04:46
● 2018-11-10 20:03:36
○ 2026-03-21 01:46:18
○ 2026-07-01 00:31:22

●NSns2.afternic.com2026-03-21 → 2026-07-01 · 3 obs

○ 2018-11-10 20:03:36
● 2026-03-21 01:46:18
● 2026-07-01 00:31:22

○NSns2.namebrightdns.com2015-06-25 → 2018-11-10 · 8 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
● 2016-02-03 17:48:14
○ 2016-04-23 17:02:24
● 2017-02-07 21:04:46
● 2018-11-10 20:03:36
○ 2026-03-21 01:46:18
○ 2026-07-01 00:31:22

○NSnsg1.namebrightdns.com2015-06-25 → 2016-04-23 · 6 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
○ 2015-11-09 02:24:58
● 2016-04-23 17:02:24
○ 2017-02-07 21:04:46
○ 2026-07-01 00:31:22

○NSnsg2.namebrightdns.com2016-04-23 → 2016-04-23 · 4 obs

○ 2016-02-03 17:48:14
● 2016-04-23 17:02:24
○ 2017-02-07 21:04:46
○ 2026-07-01 00:31:22

●NSverification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn2026-03-21 → 2026-07-01 · 3 obs

○ 2018-11-10 20:03:36
● 2026-03-21 01:46:18
● 2026-07-01 00:31:22

○MXanmail.namebrightmail.com2015-06-25 → 2015-06-25 · 4 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
○ 2015-11-09 02:24:58
○ 2026-07-01 00:31:22

○MXmailstore1.secureserver.net2008-03-14 → 2008-03-14 · 3 obs

● 2008-03-14 15:26:32
○ 2015-06-25 10:30:58
○ 2026-07-01 00:31:22

○MXsmtp.secureserver.net2008-03-14 → 2008-03-14 · 3 obs

● 2008-03-14 15:26:32
○ 2015-06-25 10:30:58
○ 2026-07-01 00:31:22

●A13.248.169.482026-03-21 → 2026-07-01 · 3 obs

○ 2018-11-10 20:03:36
● 2026-03-21 01:46:18
● 2026-07-01 00:31:22

○A34.196.72.622017-02-07 → 2017-02-07 · 4 obs

○ 2016-04-23 17:02:24
● 2017-02-07 21:04:46
○ 2018-11-10 20:03:36
○ 2026-07-01 00:31:22

○A52.0.96.242016-02-03 → 2016-02-03 · 4 obs

○ 2015-11-09 02:24:58
● 2016-02-03 17:48:14
○ 2016-04-23 17:02:24
○ 2026-07-01 00:31:22

○A52.200.243.1232016-04-23 → 2016-04-23 · 4 obs

○ 2016-02-03 17:48:14
● 2016-04-23 17:02:24
○ 2017-02-07 21:04:46
○ 2026-07-01 00:31:22

○A52.22.211.552016-02-03 → 2016-02-03 · 4 obs

○ 2015-11-09 02:24:58
● 2016-02-03 17:48:14
○ 2016-04-23 17:02:24
○ 2026-07-01 00:31:22

○A54.152.144.2432016-04-23 → 2016-04-23 · 4 obs

○ 2016-02-03 17:48:14
● 2016-04-23 17:02:24
○ 2017-02-07 21:04:46
○ 2026-07-01 00:31:22

○A54.174.31.2542015-06-25 → 2015-11-09 · 5 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
● 2015-11-09 02:24:58
○ 2016-02-03 17:48:14
○ 2026-07-01 00:31:22

○A54.208.74.2152015-06-25 → 2015-11-09 · 5 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
● 2015-11-09 02:24:58
○ 2016-02-03 17:48:14
○ 2026-07-01 00:31:22

○A54.82.156.192017-02-07 → 2017-02-07 · 4 obs

○ 2016-04-23 17:02:24
● 2017-02-07 21:04:46
○ 2018-11-10 20:03:36
○ 2026-07-01 00:31:22

○A68.178.232.1002008-03-14 → 2008-03-14 · 3 obs

● 2008-03-14 15:26:32
○ 2015-06-25 10:30:58
○ 2026-07-01 00:31:22

●A76.223.54.1462026-03-21 → 2026-07-01 · 3 obs

○ 2018-11-10 20:03:36
● 2026-03-21 01:46:18
● 2026-07-01 00:31:22

○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-06-25 → 2016-04-23 · 5 obs

○ 2008-03-14 15:26:32
● 2015-06-25 10:30:58
● 2016-04-23 17:02:24
○ 2017-02-07 21:04:46
○ 2026-07-01 00:31:22

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-02-07 → 2018-11-10 · 5 obs

○ 2016-04-23 17:02:24
● 2017-02-07 21:04:46
● 2018-11-10 20:03:36
○ 2026-03-21 01:46:18
○ 2026-07-01 00:31:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net...	-
weddingtask.com	ns1.afternic.com, ns2.afternic.com, verification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingtask.com (unsigned zone)

⏱️ Timing

Total: 3313ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

weddingtask.com resolves to the IP addresses 13.248.169.48 and 76.223.54.146

Among the host names that share IP numbers with weddingtask.com are protect02.vaultonline.com, nardi.org, deeptexas.xyz and two others.

Name Servers

weddingtask.com is served by three name servers: ns1.afternic.com, ns2.afternic.com and verification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn.

weddingtask.com shares at least some of its name servers with other domains, including listy.io, memphisbooks.com, healingsingles.com and two others.

These name servers are frequently paired with the name servers launch1.spaceship.net, launch2.spaceship.net and verification-jz2jmwqdqoxci4jvnbftxx.ns101.verify.hn.

The hostnames ns1.afternic.com, ns2.afternic.com and verification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn each direct to two IP addresses — ns1.afternic.com to 97.74.98.69 and 2603:5:2126::45, ns2.afternic.com to 173.201.66.69 and 2603:5:2226::45, and verification-frb6pqdkkjlns5j4tthxc3.ns101.verify.hn to 13.248.169.48 and 76.223.54.146.