contenttechnology.net - dns.ninja
contenttechnology.net
net
| 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=1786061599 | ||||||
Same first word
contenttechnology.net |
DNS History
15 records (9 active, 6 former)
○NSns1.sitelutions.com2015-06-16 → 2016-07-01 · 4 obs
● 2016-07-01 16:26:02
○ 2017-02-15 16:36:50
○ 2026-08-07 00:29:02
○NSns2.sitelutions.com2015-06-16 → 2016-07-01 · 4 obs
● 2016-07-01 16:26:02
○ 2017-02-15 16:36:50
○ 2026-08-07 00:29:02
○NSns3.sitelutions.com2015-06-16 → 2016-07-01 · 4 obs
● 2016-07-01 16:26:02
○ 2017-02-15 16:36:50
○ 2026-08-07 00:29:02
○NSns4.sitelutions.com2015-06-16 → 2016-07-01 · 4 obs
● 2016-07-01 16:26:02
○ 2017-02-15 16:36:50
○ 2026-08-07 00:29:02
○NSns5.sitelutions.com2015-06-16 → 2016-07-01 · 4 obs
● 2016-07-01 16:26:02
○ 2017-02-15 16:36:50
○ 2026-08-07 00:29:02
●NSns55.domaincontrol.com2026-03-26 → 2026-08-07 · 3 obs
● 2026-03-26 05:40:32
● 2026-08-07 00:29:02
●NSns56.domaincontrol.com2026-03-26 → 2026-08-07 · 3 obs
● 2026-03-26 05:40:32
● 2026-08-07 00:29:02
●MXalt1.aspmx.l.google.com2026-03-26 → 2026-08-07 · 2 obs
● 2026-08-07 00:29:02
●MXalt2.aspmx.l.google.com2026-03-26 → 2026-08-07 · 2 obs
● 2026-08-07 00:29:02
●MXalt3.aspmx.l.google.com2026-03-26 → 2026-08-07 · 2 obs
● 2026-08-07 00:29:02
●MXalt4.aspmx.l.google.com2026-03-26 → 2026-08-07 · 2 obs
● 2026-08-07 00:29:02
●MXaspmx.l.google.com2026-03-26 → 2026-08-07 · 2 obs
● 2026-08-07 00:29:02
●A15.197.148.332026-03-26 → 2026-08-07 · 3 obs
● 2026-03-26 05:40:32
● 2026-08-07 00:29:02
●A3.33.130.1902026-03-26 → 2026-08-07 · 3 obs
● 2026-03-26 05:40:32
● 2026-08-07 00:29:02
○A84.19.169.1102015-06-16 → 2016-07-01 · 4 obs
● 2016-07-01 16:26:02
○ 2017-02-15 16:36:50
○ 2026-08-07 00:29:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | j.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net... | - |
| contenttechnology.net | ns55.domaincontrol.com, ns56.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.75.28
NS records: ns55.domaincontrol.com, ns56.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for contenttechnology.net (unsigned zone)
⏱️ Timing
Total: 314ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns55.domaincontrol.com, ns56.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=vpiaOP3gLUWSU0w, v=spf1 include:dc-aa8e722993._spfm.conte |
| SOA | 1 | ns55.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
contenttechnology.net resolves to the IP addresses 3.33.130.190 and 15.197.148.33
Among the host names that share IP numbers with contenttechnology.net are rorschachmg.com, miraclesinminutes.com, 1-type.com and two others.
Name Servers
The NS records for contenttechnology.net delegate to ns55.domaincontrol.com and ns56.domaincontrol.com.
contenttechnology.net has the same name server delegation as a number of other domains, such as imxsnd115.com, sgittech.com, orangerec.com and two more.
contenttechnology.net has a partial name server overlap with other domains — among them vigeomedia.com and daxparts.com.
ns55.domaincontrol.com resolves to 97.74.107.28 and 2603:5:21b2::1c. Likewise, ns56.domaincontrol.com resolves to 173.201.75.28 and 2603:5:22b2::1c — two IP addresses apiece.
Mail Servers
contenttechnology.net is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
contenttechnology.net shares at least some of its mail servers with other domains — for example ns500693.ns500734.ns500693.ns500734.ns500699.ns500699.ns500693.ns500588.ns500588.ns500699.ns500612.ns500612.ns500588.ns500612.dtrkdll.com, ns500731.ns500671.ns500671.ns500754.ns500704.ns500688.ns500671.ns500671.ns500688.ns500705.ns500671.ns500131.lustychickser.com, ns500754.ns500742.ns500742.ns500671.ns500754.ns500742.ns500705.ns500678.ns500705.ns500291.ns500291.ns500649.ns500142.lusty(0x736c7574)z.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
The A records for aspmx.l.google.com return 192.178.218.26 and 2607:f8b0:4004:c1d::1a.
The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1a.
The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1b.
The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1b.
The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1b.