meetmidgard.com - robtex.com
meetmidgard.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | 9eaab87e-c1ea-402f-884c-75b2a0482531 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1781998370 | ||||||
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=1784166452 | ||||||
Same first word
meetmidgard.com |
DNS History
4 records (4 active, 0 former)
●NSlaunch1.spaceship.net2026-05-24 → 2026-07-16 · 2 obs
● 2026-07-16 02:01:38
●NSlaunch2.spaceship.net2026-05-24 → 2026-07-16 · 2 obs
● 2026-07-16 02:01:38
●A44.232.173.2492026-05-24 → 2026-07-16 · 2 obs
● 2026-07-16 02:01:38
●A52.40.42.1132026-05-24 → 2026-07-16 · 2 obs
● 2026-07-16 02:01:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| meetmidgard.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for meetmidgard.com (unsigned zone)
⏱️ Timing
Total: 505ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 9eaab87e-c1ea-402f-884c-75b2a0482531 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
meetmidgard.com resolves to the IP addresses 44.232.173.249 and 52.40.42.113
Additional host names — pelvic.ai, smartaccess.xyz, mistera.com and two others — share IP numbers with meetmidgard.com.
Name Servers
Two name servers handle the delegation for meetmidgard.com: launch1.spaceship.net and launch2.spaceship.net.
meetmidgard.com shares its name server setup with other domains, including trct.com, legendaryeast.com, xn--mgbcv2b2c.com and two others.
meetmidgard.com has at least partial name server overlap with other domains, such as nossamusica.com, highlinefitness.com, thisismedical.com and two others.
It is common to find these name servers paired with the name servers verification-mdzaaqbc9wh5xb8j4cudbd.ns101.verify.hn.
launch1.spaceship.net and launch2.spaceship.net both carry two IP addresses. The A records for launch1.spaceship.net are 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26; the A records for launch2.spaceship.net are 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.