code4monitoring.com - dns.ninja
code4monitoring.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=1789334708 | ||||||
Same first word
code4monitoring.com |
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSns69.domaincontrol.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●NSns70.domaincontrol.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●MXalt1.aspmx.l.google.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●MXalt2.aspmx.l.google.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●MXalt3.aspmx.l.google.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●MXalt4.aspmx.l.google.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●MXaspmx.l.google.com2026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
●A132.148.180.452026-09-09 → 2026-09-13 · 2 obs
● 2026-09-13 21:42:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| code4monitoring.com | ns69.domaincontrol.com, ns70.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.104.45
NS records: ns69.domaincontrol.com, ns70.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for code4monitoring.com (unsigned zone)
⏱️ Timing
Total: 354ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 132.148.180.45 |
| NS | 2 | ns69.domaincontrol.com, ns70.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=EJiyvhk5ShAae_K, v=spf1 include:dc-aa8e722993._spfm.code4 |
| SOA | 1 | ns69.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns69.domaincontrol.com, ns69.domaincontrol.com, ns70.domaincontrol.com...)
Analysis
IP Addresses
code4monitoring.com has exactly one IP address — 132.148.180.45.
sagxperience.com, blacblok.com, liveintunehealth.com plus two other host names have IP numbers in common with code4monitoring.com.
Name Servers
code4monitoring.com uses two name servers for its delegation: ns69.domaincontrol.com and ns70.domaincontrol.com.
The name server configuration of code4monitoring.com is shared with other domains, for instance ethicalhackerz.in, equinebiogenieireland.com, rentametaplane.com and two others.
The two host names ns69.domaincontrol.com and ns70.domaincontrol.com each have a pair of IP addresses: ns69.domaincontrol.com has 97.74.104.45 and 2603:5:2184::2d, and ns70.domaincontrol.com has 173.201.72.45 and 2603:5:2284::2d.
Mail Servers
code4monitoring.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by code4monitoring.com are shared with other domains: trinitiprecisionlabs.com, lsgranite.com, ksprocesstech.jp and two others among them.
These mail servers are often deployed together with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c19::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.