belforalert.com - robtex.com
belforalert.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 | ||||||
DNS History
19 records (8 active, 11 former)
○NSdns1.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○NSdns2.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○NSdns3.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○NSdns4.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○NSdns5.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
●NSns41.domaincontrol.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
●NSns42.domaincontrol.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
●MXalt1.aspmx.l.google.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
●MXalt2.aspmx.l.google.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
●MXalt3.aspmx.l.google.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
●MXalt4.aspmx.l.google.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
●MXaspmx.l.google.com2026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
○MXeforward1.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○MXeforward2.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○MXeforward3.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○MXeforward4.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
○MXeforward5.registrar-servers.com2016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
●A168.235.111.1132026-03-09 → 2026-03-09 · 2 obs
● 2026-03-09 20:12:36
○A216.152.136.932016-12-14 → 2016-12-25 · 3 obs
● 2016-12-25 07:47:02
○ 2026-03-09 20:12:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net... | - |
| belforalert.com | ns41.domaincontrol.com, ns42.domaincontrol.com | 4 records |
✅ Authoritative Response
Server: 173.201.68.21
NS records: ns41.domaincontrol.com, ns42.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for belforalert.com (unsigned zone)
⏱️ Timing
Total: 130ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 168.235.111.113 |
| NS | 2 | ns41.domaincontrol.com, ns42.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 19)... |
| TXT | 4 | google-site-verification=rHAcbijtHjBd8fO, wombat-verification=3KwxVCQV1HEp-aRXRTKK... |
| SOA | 1 | ns41.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns41.domaincontrol.com, ns41.domaincontrol.com, ns42.domaincontrol.com...)
Analysis
IP Addresses
belforalert.com maps to IP address 168.235.111.113.
Other host names, for instance hoodz.us.com, obpfs.com, zplumberz.com, bamcor.net and 1800waterdamage.com share IP numbers with belforalert.com.
Name Servers
Two name servers ns41.domaincontrol.com and ns42.domaincontrol.com are delegated to belforalert.com.
belforalert.com uses the same name server configuration as other domains, such as suzycleaning.com, canaryfi.com, hrtins.com, oaohn.org and hapsta.com.
Host names with two IPs:
ns41.domaincontrol.com points to 2603:5:2142::15 and 97.74.100.21.
ns42.domaincontrol.com points to 2603:5:2242::15 and 173.201.68.21.
Mail Servers
belforalert.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
belforalert.com shares mail servers with other domains at least in part, for instance ns500737.ns500724.ns500599.ns500599.ns500737.ns500724.ns500583.ns500599.ns500599.ns500682.ns500599.yummyflingsfinder.com, sampsonandsons.com, ns500698.ns500698.ns500759.ns500698.ns500698.ns500698.ns500735.ns500735.ns500576.ns500576.ns500708.ns500576.ns500686.ns500576.ns500619.trackreceptor.com, ns500758.ns500758.ns500698.ns500735.ns500698.ns500735.ns500698.ns500735.ns500698.ns500736.ns500708.ns500576.ns500698.ns500698.ns500576.ns500619.ns500576.trackreceptor.com and ns500671.ns500754.ns500754.ns500754.ns500704.ns500731.ns500671.ns500704.ns500671.ns500671.ns500671.ns500649.ns500666.ns500291.ns500131.lustychickser.com.
These mail servers are often used together with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Two IPs per host name:
aspmx.l.google.com points to: 2607:f8b0:4004:c19::1b and 172.253.62.27
alt1.aspmx.l.google.com points to: 2607:f8b0:4003:c30::1b and 74.125.27.26
alt2.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.26
alt3.aspmx.l.google.com points to: 2607:f8b0:4024:c0d::1b and 192.178.152.26
alt4.aspmx.l.google.com points to: 2607:f8b0:4023:403::1a and 142.250.96.27
Pattern: left IDs ascend by 9 (12, 21, 30, 39, 48); each pair of targets ascend by 9 (15/18, 24/27, 33/36, 42/45, 51/54)