weddinghq.com - robtex.com
weddinghq.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.squadhelp.com ⭐ | ||||||
| A | 52.201.79.206🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix | ||||||
| PTR | ec2-52-201-79-206.compute-1.amazonaws.com | ||||||
| NS | ns2.squadhelp.com | ||||||
| A | 52.23.148.124🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-23-148-124.compute-1.amazonaws.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.squadhelp.comhostmaster@weddinghq.com 2024-03-05 #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.netnstld@verisign-grs.com serial=1774660557 | ||||||
Same first word
weddinghq.co.uk |
weddinghq.com |
DNS History
21 records (3 active, 18 former)
○NSns-1521.awsdns-62.org2016-05-02 → 2016-05-02 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○NSns-1956.awsdns-52.co.uk2016-05-02 → 2016-05-02 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○NSns-237.awsdns-29.com2016-05-02 → 2016-05-02 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○NSns-783.awsdns-33.net2016-05-02 → 2016-05-02 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
●NSns1.squadhelp.com2026-03-28 → 2026-03-28 · 2 obs
○ 2017-03-25 23:01:56
● 2026-03-28 01:30:52
● 2026-03-28 01:30:52
●NSns2.squadhelp.com2026-03-28 → 2026-03-28 · 2 obs
○ 2017-03-25 23:01:56
● 2026-03-28 01:30:52
● 2026-03-28 01:30:52
○NSns21.ixwebhosting.com2017-03-25 → 2017-03-25 · 3 obs
○ 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○NSns22.ixwebhosting.com2017-03-25 → 2017-03-25 · 3 obs
○ 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○NSns23.ixwebhosting.com2015-08-03 → 2015-12-03 · 4 obs
● 2015-08-03 23:31:12
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
○NSns24.ixwebhosting.com2015-08-03 → 2015-12-03 · 4 obs
● 2015-08-03 23:31:12
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
○MXalt1.aspmx.l.google.com2015-08-03 → 2017-03-25 · 3 obs
● 2015-08-03 23:31:12
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○MXalt2.aspmx.l.google.com2015-08-03 → 2017-03-25 · 3 obs
● 2015-08-03 23:31:12
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○MXalt3.aspmx.l.google.com2016-05-02 → 2017-03-25 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○MXalt4.aspmx.l.google.com2016-05-02 → 2017-03-25 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○MXaspmx.l.google.com2015-08-03 → 2017-03-25 · 3 obs
● 2015-08-03 23:31:12
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○MXaspmx2.googlemail.com2015-08-03 → 2015-12-03 · 4 obs
● 2015-08-03 23:31:12
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
○MXaspmx3.googlemail.com2015-08-03 → 2015-12-03 · 4 obs
● 2015-08-03 23:31:12
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
○A50.6.50.952015-08-03 → 2015-12-03 · 4 obs
● 2015-08-03 23:31:12
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
● 2015-12-03 01:48:42
○ 2016-05-02 20:23:16
○ 2026-03-28 01:30:52
●A52.20.84.622026-03-28 → 2026-03-28 · 2 obs
○ 2017-03-25 23:01:56
● 2026-03-28 01:30:52
● 2026-03-28 01:30:52
○A52.49.138.482016-05-02 → 2016-05-02 · 4 obs
○ 2015-12-03 01:48:42
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2016-05-02 20:23:16
○ 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
○A72.41.18.22017-03-25 → 2017-03-25 · 3 obs
○ 2016-05-02 20:23:16
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
● 2017-03-25 23:01:56
○ 2026-03-28 01:30:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net... | - |
| weddinghq.com | ns1.squadhelp.com, ns2.squadhelp.com | 2 records |
✅ Authoritative Response
Server:52.23.148.124
NS records: ns1.squadhelp.com, ns2.squadhelp.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for weddinghq.com (unsigned zone)
⏱️ Timing
Total: 358ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.squadhelp.com, ns1.squadhelp.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.squadhelp.com hostmaster.weddinghq.c |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.squadhelp.com, ns2.squadhelp.com)
Analysis
IP Addresses
weddinghq.com points to IP number: 52.20.84.62.
Other host names such as xi4.com, chartinsider.com, pchains.com, vidnol.com and bmb.agency share IPs with weddinghq.com.
Name Servers
weddinghq.com is delegated to two name servers: ns1.squadhelp.com and ns2.squadhelp.com.
weddinghq.com shares the same name server setup as sivvia.com, playit.co, checkbud.com, eliteforce.org and tevola.com.
weddinghq.com shares some name servers with other domains, for instance texasfumigation.com.
Host names with a single IP:
ns1.squadhelp.com points to 52.201.79.206.
ns2.squadhelp.com points to 52.23.148.124.