weddingcard.com - robtex.com
weddingcard.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.atom.com β | ||||||
| A | 44.219.81.145πΊπΈ Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86πΊπΈ Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@weddingcard.com 2025-11-10 #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=1774520582 | ||||||
Same first word
weddingcard.jp |
weddingcard.it |
weddingcard.in |
weddingcard.ca |
weddingcard.net |
weddingcard.eu |
weddingcard.ru |
weddingcard.org |
weddingcard.com.au |
weddingcard.de |
weddingcard.com |
weddingcard.my |
DNS History
16 records (3 active, 13 former)
βNSbuy.internettraffic.com2015-06-14 β 2015-11-07 Β· 5 obs
β 2015-06-14 23:40:18
β 2015-11-07 14:26:20
β 2016-02-29 05:31:44
β 2026-03-26 10:37:58
βNSlaunch1.spaceship.net2026-02-17 β 2026-02-28 Β· 5 obs
β 2026-02-17 06:28:32
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-26 10:37:58
βNSlaunch2.spaceship.net2026-02-17 β 2026-02-28 Β· 5 obs
β 2026-02-17 06:28:32
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-26 10:37:58
βNSns1.atom.com2026-03-24 β 2026-03-26 Β· 3 obs
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βNSns1.sedoparking.com2016-02-29 β 2026-03-08 Β· 8 obs
β 2016-02-29 05:31:44
β 2017-06-02 15:05:50
β 2026-02-17 06:28:32
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βNSns2.atom.com2026-03-24 β 2026-03-26 Β· 3 obs
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βNSns2.sedoparking.com2016-02-29 β 2026-03-08 Β· 8 obs
β 2016-02-29 05:31:44
β 2017-06-02 15:05:50
β 2026-02-17 06:28:32
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βNSsell.internettraffic.com2015-06-14 β 2015-11-07 Β· 5 obs
β 2015-06-14 23:40:18
β 2015-11-07 14:26:20
β 2016-02-29 05:31:44
β 2026-03-26 10:37:58
βMXlocalhost2016-09-16 β 2026-03-08 Β· 8 obs
β 2016-09-16 13:59:58
β 2026-02-17 06:28:32
β 2026-02-27 14:05:52
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βMXmail.nickstel.com2016-02-29 β 2016-06-20 Β· 4 obs
β 2016-06-20 22:37:06
β 2016-09-16 13:59:58
β 2026-03-26 10:37:58
βA44.232.173.2492026-02-17 β 2026-02-28 Β· 5 obs
β 2026-02-17 06:28:32
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-26 10:37:58
βA52.20.84.622026-03-24 β 2026-03-26 Β· 3 obs
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βA52.40.42.1132026-02-17 β 2026-02-28 Β· 5 obs
β 2026-02-17 06:28:32
β 2026-02-28 11:56:24
β 2026-03-08 05:55:04
β 2026-03-26 10:37:58
βA64.190.63.2222026-03-08 β 2026-03-08 Β· 4 obs
β 2026-03-08 05:55:04
β 2026-03-24 05:54:38
β 2026-03-26 10:37:58
βA69.172.201.2082015-06-14 β 2015-11-07 Β· 5 obs
β 2015-06-14 23:40:18
β 2015-11-07 14:26:20
β 2016-02-29 05:31:44
β 2026-03-26 10:37:58
βA72.52.4.1202016-02-29 β 2017-06-02 Β· 5 obs
β 2016-02-29 05:31:44
β 2017-06-02 15:05:50
β 2026-02-17 06:28:32
β 2026-03-26 10:37:58
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| weddingcard.com | ns1.atom.com, ns2.atom.com | 2 records |
β Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for weddingcard.com (unsigned zone)
β±οΈ Timing
Total: 3619ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.weddingcard.com |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
weddingcard.com points to a single IP number: 52.20.84.62.
Other host names, for instance robocor.com, bcgg.com, soffie.com, isassist.com and roasters.us share IP numbers with weddingcard.com.
Name Servers
weddingcard.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
weddingcard.com uses the same name server setup as other domains, for instance airports.cc, zuwat.com, meekah.com, pilotpin.com and herowizard.com.
weddingcard.com shares name servers with other domains at least partially, for instance tekit.com, revoox.com, rankbin.com, rushname.com and bottoys.com.
these name servers are often used together with the name servers verification-8uneycqadhrltns2lewzss.ns101.verify.hn.
Host names with one IP number:
ns1.atom.com points to: 44.219.81.145.
ns2.atom.com points to: 50.19.240.86.