corridorfunding.com - robtex.com
corridorfunding.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=1774427447 | ||||||
Same first word
corridorfunding.com |
DNS History
11 records (10 active, 1 former)
●NSns-cloud-b1.googledomains.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●NSns-cloud-b2.googledomains.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●NSns-cloud-b3.googledomains.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●NSns-cloud-b4.googledomains.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●MXalt1.aspmx.l.google.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●MXalt2.aspmx.l.google.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●MXalt3.aspmx.l.google.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●MXalt4.aspmx.l.google.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
●MXaspmx.l.google.com2016-04-03 → 2026-03-25 · 2 obs
● 2026-03-25 08:31:14
○A199.34.228.552016-04-03 → 2017-04-08 · 4 obs
● 2017-04-08 19:23:36
○ 2026-02-18 00:24:24
○ 2026-03-25 08:31:14
●A199.60.103.462026-02-18 → 2026-03-25 · 3 obs
● 2026-02-18 00:24:24
● 2026-03-25 08:31:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| corridorfunding.com | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.107
NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for corridorfunding.com (unsigned zone)
⏱️ Timing
Total: 327ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.60.103.46 |
| NS | 4 | ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:_spf.google.com ~all, apple-domain-verification=eWWkRiY4wefinM |
| SOA | 1 | ns-cloud-b1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)
Analysis
IP Addresses
corridorfunding.com resolves to one IP number: 199.60.103.46.
other host names including dstny.se, ecoinsulation.co.nz, drf-akademie.de, quarryhilladvisors.com and drf-luftrettung-notfalltrainings.de share IP numbers with corridorfunding.com.
Name Servers
corridorfunding.com is delegated to four name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
corridorfunding.com at least partially shares name servers with other domains, for instance uraniumspot.com, fxpopup.com, jeffreydizon.com, browserbee.com and cocospetmarket.com.
Host names with two IP numbers:
ns-cloud-b1.googledomains.com points to 2001:4860:4802:32::6b and 216.239.32.107; ns-cloud-b2.googledomains.com points to 2001:4860:4802:34::6b and 216.239.34.107; ns-cloud-b3.googledomains.com points to 2001:4860:4802:36::6b and 216.239.36.107; ns-cloud-b4.googledomains.com points to 2001:4860:4802:38::6b and 216.239.38.107.
Mail Servers
corridorfunding.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.
corridorfunding.com shares some mail servers with other domains, at least partially, for instance ns500754.ns500671.ns500731.ns500671.ns500731.ns500742.ns500688.ns500671.ns500678.ns500671.ns500649.ns500688.ns500671.ns500649.lustychickser.com, pchsc.org, fashionwish.com, ns500765.ns500699.ns500693.ns500693.ns500693.ns500693.ns500699.ns500588.ns500699.ns500683.ns500588.ns500588.ns500612.ns500612.ns500110.dtrkdll.com and ns500693.ns500693.ns500693.ns500693.ns500699.ns500683.ns500693.ns500612.ns500588.ns500588.dtrkdll.com.
These mail servers are commonly used alongside aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4023:c0d::1b and 142.250.141.27
alt1.aspmx.l.google.com points to 2a00:1450:4025:402::1a and 142.250.102.27
alt2.aspmx.l.google.com points to 2a00:1450:4013:c1e::1b and 192.178.213.26
alt3.aspmx.l.google.com points to 2a00:1450:4001:c21::1a and 142.251.127.27
alt4.aspmx.l.google.com points to 2a00:1450:4025:c01::1b and 142.250.147.26