intrasema.com - robtex.com
intrasema.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=1771291435 | ||||||
MX for
intrasema.com |
Up
www.intrasema.com |
Same first word
intrasema.com |
Similar names
DNS History
12 records (9 active, 3 former)
○NSns1.cloud05.brixly.uk2017-05-09 → 2017-05-09 · 2 obs
○ 2026-02-22 13:38:42
●NSns1.mysecurecloudhost.com2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 13:38:42
○NSns2.cloud05.brixly.uk2017-05-09 → 2017-05-09 · 2 obs
○ 2026-02-22 13:38:42
●NSns2.mysecurecloudhost.com2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 13:38:42
●NSns3.mysecurecloudhost.com2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 13:38:42
●NSns4.mysecurecloudhost.com2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 13:38:42
●MXintrasema.com2017-05-09 → 2026-02-22 · 2 obs
● 2026-02-22 13:38:42
●A195.250.26.522026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 13:38:42
○A83.136.254.1432017-05-09 → 2017-05-09 · 2 obs
○ 2026-02-22 13:38:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| intrasema.com | ns1.tks.pe, ns2.tks.pe, ns3.tks.pe | - |
✅ Authoritative Response
Server: 76.223.26.245
NS records: ns1.tks.pe, ns2.tks.pe, ns3.tks.pe
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for intrasema.com (unsigned zone)
⏱️ Timing
Total: 225ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 195.250.26.52 |
| NS | 4 | ns4.mysecurecloudhost.com, ns1.mysecurecloudhost.com... |
| MX | 1 | intrasema.com (pri: 0) |
| TXT | 1 | v=spf1 ip4:195.250.26.52 include:spf.mys |
| SOA | 1 | ns1.mysecurecloudhost.com servers.mysecu |
AI analysis
www.intrasema.com is a child of intrasema.com.
intrasema.com serves as the mail server for intrasema.com.
intrasema.com resolves to one IP number: 195.250.26.52.
Other host names, for instance _dc-mx.0d65b5549a19.articleslift.com, _dc-mx.0e3ede655f9e.geonewss.com, bodybuildingdoctor.com, _dc-mx.2b4a76a3ba97.art-kust.com and raftertc.com share IP numbers with intrasema.com.
intrasema.com is delegated to seven name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com, ns1.tks.pe, ns2.tks.pe and ns3.tks.pe.
intrasema.com at least partially shares name servers with other domains, including agedcareconnect.com.au, lajmeshqip.info, jesusisthesaviour.com, calendardream.com and maxline-group.com.
These name servers are commonly used with ns4.tks.pe, ns1.a2hosting.com, ns2.a2hosting.com, ns3.a2hosting.com, ns4.a2hosting.com and ns1.supercp.com.
Host names with one IP number:
ns1.mysecurecloudhost.com points to 13.248.158.180.
ns2.mysecurecloudhost.com points to 75.2.118.134.
ns3.mysecurecloudhost.com points to 76.223.26.245.
ns4.mysecurecloudhost.com points to 99.83.147.209.
ns1.tks.pe points to 13.248.158.180.
ns2.tks.pe points to 75.2.118.134.
ns3.tks.pe points to 76.223.26.245.
Hosts pointing to 13.248.158.180: ns1.mysecurecloudhost.com, ns1.tks.pe.
Hosts pointing to 75.2.118.134: ns2.mysecurecloudhost.com, ns2.tks.pe.
Hosts pointing to 76.223.26.245: ns3.mysecurecloudhost.com, ns3.tks.pe.
intrasema.com is handled by a single mail server, intrasema.com.
Host name intrasema.com resolves to a single IP: 195.250.26.52.