engineeringapi.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

engineeringapi.com

DNSSEC⚠️ Not signed
A208.91.197.39🇻🇬 CONFLUENCE-NETWORK-INC208.91.197.0/24 Confluence Networks Route Object
NSdns101.register.com ⭐
A162.159.24.117Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSdns102.register.com
A162.159.25.158Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
SOADNS101.REGISTER.comroot@REGISTER.com serial=125052210

com

Same first word

Similar names

Previous names

Next names

DNS History

15 records (3 active, 12 former)

2020202120222023202420252026NSdns101.register.comdns102.register.comdns1.registrar-servers.comdns2.registrar-servers.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA208.91.197.39192.64.119.219216.239.32.21216.239.34.21216.239.36.21216.239.38.21
○NSdns1.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
●NSdns101.register.com2026-08-18 → 2026-10-23 · 3 obs
○ 2019-12-17 12:22:16
● 2026-08-18 04:04:12
● 2026-10-23 16:22:30
●NSdns102.register.com2026-08-18 → 2026-10-23 · 3 obs
○ 2019-12-17 12:22:16
● 2026-08-18 04:04:12
● 2026-10-23 16:22:30
○NSdns2.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○MXeforward1.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○MXeforward2.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○MXeforward3.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○MXeforward4.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○MXeforward5.registrar-servers.com2019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○A192.64.119.2192019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
●A208.91.197.392026-08-18 → 2026-10-23 · 5 obs
○ 2019-12-17 12:22:16
● 2026-08-18 04:04:12
○ 2026-10-09 13:46:08
● 2026-10-11 00:24:36
● 2026-10-23 16:22:30
○A216.239.32.212019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○A216.239.34.212019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○A216.239.36.212019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30
○A216.239.38.212019-12-17 → 2019-12-17 · 3 obs
● 2019-12-17 12:22:16
○ 2026-08-18 04:04:12
○ 2026-10-23 16:22:30

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
engineeringapi.comdns101.register.com, dns102.register.com2 records

✅ Authoritative Response

Server:162.159.24.117

NS records: dns101.register.com, dns102.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for engineeringapi.com (unsigned zone)

⏱️ Timing

Total: 414ms | Queries: -

📄 Records

TypeCountSample Data
A1208.91.197.39
NS2dns102.register.com, dns101.register.com
SOA1DNS101.REGISTER.com root.REGISTER.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

IP Addresses

engineeringapi.com has exactly one IP address — 208.91.197.39.

terrypreuss.com, pauldavidbutterfield.com, 618hampton.com plus two other host names have IP numbers in common with engineeringapi.com.

Name Servers

engineeringapi.com has two authoritative name servers — dns101.register.com and dns102.register.com.

The name server configuration of engineeringapi.com is shared with other domains, for instance wolfhollow.ca, desanctisins.net, cbfhouse.com and two others.

The name servers for engineeringapi.com overlap at least partially with those of other domains — for example ipgo.net.

Both dns101.register.com and dns102.register.com have a single IP address each — dns101.register.com resolves to 162.159.24.117 while dns102.register.com resolves to 162.159.25.158.