method.engineering - dns.ninja

method.engineering

DNSSEC⚠️ Not signed
A44.232.173.249πŸ‡ΊπŸ‡Έ Amazon44.224.0.0/11 EC2 PDX prefix
PTRec2-44-232-173-249.us-west-2.compute.amazonaws.com
A52.40.42.113πŸ‡ΊπŸ‡Έ Amazon52.40.0.0/14 EC2 PDX prefix
NSlaunch1.spaceship.net ⭐
A2400:cb00:2049:1::a29f:1a26πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSlaunch2.spaceship.net
A2400:cb00:2049:1::a29f:1b20πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
TXT3d8cb410-3ea4-47c7-a0a3-5d16a382e266
TXT8b2722986d7b091471343b14e403ad4193981ed6
SOAlaunch1.spaceship.netsupport@spaceship.com serial=1781722972

engineering

DNSSECπŸ”’ Signed (DS record present)
NSv0n0.nic.engineering ⭐
NSv0n1.nic.engineering
NSv0n2.nic.engineering
NSv0n3.nic.engineering
NSv2n0.nic.engineering
NSv2n1.nic.engineering
SOAv0n0.nic.engineeringhostmaster@donuts.email serial=1784956106

Same first word

Similar names

DNS History

17 records (4 active, 13 former)

2017201820192020202120222023202420252026NSlaunch1.spaceship.netlaunch2.spaceship.netdns1.p03.nsone.netdns2.p03.nsone.netdns3.p03.nsone.netdns4.p03.nsone.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA44.232.173.24952.40.42.113198.185.159.144198.185.159.145198.49.23.144198.49.23.145
β—‹NSdns1.p03.nsone.net2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹NSdns2.p03.nsone.net2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹NSdns3.p03.nsone.net2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹NSdns4.p03.nsone.net2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
●NSlaunch1.spaceship.net2026-04-23 β†’ 2026-07-25 Β· 3 obs
β—‹ 2017-08-11 15:04:32
● 2026-04-23 21:50:12
● 2026-07-25 05:53:00
●NSlaunch2.spaceship.net2026-04-23 β†’ 2026-07-25 Β· 3 obs
β—‹ 2017-08-11 15:04:32
● 2026-04-23 21:50:12
● 2026-07-25 05:53:00
β—‹MXalt1.aspmx.l.google.com2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹MXalt2.aspmx.l.google.com2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹MXalt3.aspmx.l.google.com2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹MXalt4.aspmx.l.google.com2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹MXaspmx.l.google.com2016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹A198.185.159.1442016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹A198.185.159.1452016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹A198.49.23.1442016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
β—‹A198.49.23.1452016-12-10 β†’ 2017-08-11 Β· 4 obs
● 2016-12-10 18:44:08
● 2017-08-11 15:04:32
β—‹ 2026-04-23 21:50:12
β—‹ 2026-07-25 05:53:00
●A44.232.173.2492026-04-23 β†’ 2026-07-25 Β· 3 obs
β—‹ 2017-08-11 15:04:32
● 2026-04-23 21:50:12
● 2026-07-25 05:53:00
●A52.40.42.1132026-04-23 β†’ 2026-07-25 Β· 3 obs
β—‹ 2017-08-11 15:04:32
● 2026-04-23 21:50:12
● 2026-07-25 05:53:00

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
engineeringv0n1.nic.engineering, v2n0.nic.engineering, v0n2.nic.engineering, v0n3.nic.engineering...12 records
method.engineeringlaunch2.spaceship.net, launch1.spaceship.net-

βœ… Authoritative Response

Server:162.159.26.38

NS records: launch2.spaceship.net, launch1.spaceship.net

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for method.engineering (unsigned zone)

⏱️ Timing

Total: 606ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A244.232.173.249, 52.40.42.113
NS2launch1.spaceship.net, launch2.spaceship.net
TXT23d8cb410-3ea4-47c7-a0a3-5d16a382e266, 8b2722986d7b091471343b14e403ad4193981ed6
SOA1launch1.spaceship.net support.spaceship.

πŸ“Œ Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n1.nic.engineering, v0n1.nic.engineering, v2n0.nic.engineering...)

Analysis

IP Addresses

method.engineering has two IP addresses: 44.232.173.249 and 52.40.42.113

ecashservice.com, iotedge.com, rw1.org and two other host names share IP numbers with method.engineering.

Name Servers

method.engineering has two authoritative name servers β€” launch1.spaceship.net and launch2.spaceship.net.

method.engineering uses the same name servers as several other domains β€” among them clarivum.top, acropolis.me.uk, ghatkhl.us and two more.

The name servers for method.engineering are partially shared with other domains like alimoh.com, bompec.com and pcsupportpro.com

These name servers commonly appear in combination with the name servers verification-mdzaaqbc9wh5xb8j4cudbd.ns101.verify.hn.

Both launch1.spaceship.net and launch2.spaceship.net have two IP addresses each. launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26; launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.