weddingforward.com - robtex.com
weddingforward.com
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=1785156442 | ||||||
rank #28877 in the tld
📈 Tranco rank: #214,181
Subdomains
www.weddingforward.com |
Same first word
weddingforward.com |
weddingforward.ca |
DNS History
10 records (10 active, 0 former)
●NSns-1390.awsdns-45.org2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●NSns-1770.awsdns-29.co.uk2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●NSns-452.awsdns-56.com2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●NSns-553.awsdns-05.net2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●MXalt1.aspmx.l.google.com2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●MXalt2.aspmx.l.google.com2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●MXaspmx.l.google.com2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●MXaspmx2.googlemail.com2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●MXaspmx3.googlemail.com2015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
●A54.209.206.1192015-07-08 → 2026-07-27 · 2 obs
● 2026-07-27 13:07:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net... | - |
| weddingforward.com | ns-553.awsdns-05.net, ns-452.awsdns-56.com, ns-1770.awsdns-29.co.uk, ns-1390.awsdns-45.org | 2 records |
✅ Authoritative Response
Server:205.251.198.234
NS records: ns-553.awsdns-05.net, ns-452.awsdns-56.com, ns-1770.awsdns-29.co.uk, ns-1390.awsdns-45.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for weddingforward.com (unsigned zone)
⏱️ Timing
Total: 326ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.209.206.119 |
| NS | 4 | ns-1390.awsdns-45.org, ns-1770.awsdns-29.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 2 | facebook-domain-verification=fpf25vugqbs, v=spf1 mx include:mxsspf.sendpulse.com i |
| SOA | 1 | ns-452.awsdns-56.com weddingforwardpros. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-452.awsdns-56.com, ns-452.awsdns-56.com)
Analysis
Hierarchy
www.weddingforward.com is a subdomain of weddingforward.com.
IP Addresses
weddingforward.com directs to one IP number, which is 54.209.206.119.
ec2-54-209-206-119.compute-1.amazonaws.com and www.weddingforward.com are among other host names that share IP numbers with weddingforward.com.
Name Servers
The domain weddingforward.com is delegated to these four name servers: ns-452.awsdns-56.com, ns-553.awsdns-05.net, ns-1390.awsdns-45.org and ns-1770.awsdns-29.co.uk.
The name servers of weddingforward.com overlap at least partially with those of other domains — among them mobon.co.kr, dqi22k99a99bl.cloudfront.net, genomichealth.co.uk and two more.
The name servers ns-262.awsdns-32.com, ns-602.awsdns-11.net and ns-1461.awsdns-54.org are commonly seen alongside these name servers.
Each of the four hosts ns-452.awsdns-56.com, ns-553.awsdns-05.net, ns-1390.awsdns-45.org and ns-1770.awsdns-29.co.uk has two IP addresses. ns-452.awsdns-56.com points to 205.251.193.196 and 2600:9000:5301:c400::1. ns-553.awsdns-05.net points to 205.251.194.41 and 2600:9000:5302:2900::1. ns-1390.awsdns-45.org points to 205.251.197.110 and 2600:9000:5305:6e00::1. ns-1770.awsdns-29.co.uk points to 205.251.198.234 and 2600:9000:5306:ea00::1.
Mail Servers
weddingforward.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
weddingforward.com shares at least some of its mail servers with other domains — for example tm-eng.jp, ns500821.ns500821.ns500821.ns500841.ns500794.ns500794.ns500821.ns500821.ns500795.ns500821.ns500794.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, abc.ru and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 172.253.122.26 and 2607:f8b0:4004:c1f::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.