factosecure.com - robtex.com
factosecure.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=1786266084 | ||||||
Same first word
factosecure.com |
Similar names
DNS History
9 records (9 active, 0 former)
●NSns33.domaincontrol.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●NSns34.domaincontrol.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●MXalt1.aspmx.l.google.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●MXalt2.aspmx.l.google.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●MXalt3.aspmx.l.google.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●MXalt4.aspmx.l.google.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●MXaspmx.l.google.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●MXsmtp.google.com2026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
●A167.99.62.1712026-05-20 → 2026-08-09 · 2 obs
● 2026-08-09 09:22:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| factosecure.com | ns33.domaincontrol.com, ns34.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.74.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for factosecure.com (unsigned zone)
⏱️ Timing
Total: 1954ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 167.99.62.171 |
| NS | 2 | ns33.domaincontrol.com, ns34.domaincontrol.com |
| MX | 6 | smtp.google.com (pri: 1), aspmx.l.google.com (pri: 1)... |
| TXT | 3 | google-gws-recovery-domain-verification=, v=spf1 redirect=_spf.mailhostbox.com... |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)
Analysis
IP Addresses
factosecure.com resolves to just one IP address, 167.99.62.171.
Name Servers
factosecure.com uses two name servers for its delegation: ns33.domaincontrol.com and ns34.domaincontrol.com.
factosecure.com shares its NS records with other domains, for example danabros.com, 445351.com, redstonefamilyrealty.com and two others.
At least some of factosecure.com's name servers are also used by other domains, among them shufaji.com.
The two host names ns33.domaincontrol.com and ns34.domaincontrol.com each have a pair of IP addresses: ns33.domaincontrol.com has 97.74.106.17 and 2603:5:21a1::11, and ns34.domaincontrol.com has 173.201.74.17 and 2603:5:22a1::11.
Mail Servers
The MX records for factosecure.com point to 6 mail servers — smtp.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.
There is at least a partial MX overlap between factosecure.com and other domains, including ns500754.ns500731.ns500742.ns500671.ns500731.ns500754.ns500705.ns500705.ns500705.ns500666.ns500131.lustychickser.com, ns500754.ns500742.ns500754.ns500704.ns500671.ns500704.ns500705.ns500678.ns500678.ns500291.ns500291.ns500291.ns500131.lustychickser.com, poroll.se and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 others.
DNS names with 9 IP addresses:
Hostname smtp.google.com directs to 142.251.163.26, 142.251.163.27 and 173.194.45.26 along with 6 other IP addresses.
Host names that have two IP addresses:
aspmx.l.google.com directs traffic to 192.179.18.27 and 2607:f8b0:4004:c08::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.26 and 2a00:1450:400b:c02::1a.
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.26 and 2a00:1450:400c:c23::1a.