remote-how.com - robtex.com
remote-how.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 | ||||||
rank #402915 in the tld
Same first word
remote-how.com |
DNS History
13 records (9 active, 4 former)
○NSns27.domaincontrol.com2017-09-08 → 2017-09-08 · 2 obs
○ 2026-03-11 10:41:52
○NSns28.domaincontrol.com2017-09-08 → 2017-09-08 · 2 obs
○ 2026-03-11 10:41:52
●NSrose.ns.cloudflare.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●NSwesley.ns.cloudflare.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●MXalt1.aspmx.l.google.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●MXalt2.aspmx.l.google.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●MXalt3.aspmx.l.google.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●MXalt4.aspmx.l.google.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●MXaspmx.l.google.com2026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
○MXremotehow-com01e.mail.protection.outlook.com2017-09-08 → 2017-09-08 · 2 obs
○ 2026-03-11 10:41:52
○A50.63.202.592017-09-08 → 2017-09-08 · 2 obs
○ 2026-03-11 10:41:52
●A75.2.70.752026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
●A99.83.190.1022026-03-11 → 2026-03-11 · 2 obs
● 2026-03-11 10:41:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net... | - |
| remote-how.com | rose.ns.cloudflare.com, wesley.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server: 108.162.193.246
NS records: rose.ns.cloudflare.com, wesley.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for remote-how.com (unsigned zone)
⏱️ Timing
Total: 227ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 99.83.190.102, 75.2.70.75 |
| NS | 2 | rose.ns.cloudflare.com, wesley.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 5 | facebook-domain-verification=9koery1zn0f, google-site-verification=IHRVE3-wVLUIkPS... |
| SOA | 1 | rose.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (rose.ns.cloudflare.com, rose.ns.cloudflare.com, rose.ns.cloudflare.com...)
Analysis
IP Addresses
remote-how.com resolves to two IP numbers: 75.2.70.75 and 99.83.190.102.
Other host names, for instance terrax-computer.org, microtraks.com, pemginc.com, danaepanopoulou.com and rentabike.dk share IP numbers with remote-how.com.
Name Servers
remote-how.com has two name servers: rose.ns.cloudflare.com and wesley.ns.cloudflare.com.
remote-how.com shares the same name server setup as other domains, for example rittgers.com, alanmiddletonlaw.com, koskoff.com, daltonlaw.com and bruceashworth.com.
remote-how.com shares some name servers with other domains, for example iswd.ru, grushevskogo9a.com, supportprotocol.pages.dev, outrch.io and csccompanies.com.
These name servers are commonly used with the name servers anastasia.ns.cloudflare.com.
Host names with six IP numbers: rose.ns.cloudflare.com points to: 2606:4700:50::adf5:3a8d, 2803:f800:50::6ca2:c08d, 2a06:98c1:50::ac40:208d, 108.162.192.141, 172.64.32.141 and 173.245.58.141; wesley.ns.cloudflare.com points to: 2606:4700:58::adf5:3bf6, 2803:f800:50::6ca2:c1f6, 2a06:98c1:50::ac40:21f6, 108.162.193.246, 172.64.33.246 and 173.245.59.246.
Mail Servers
remote-how.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.
remote-how.com shares some mail servers with other domains, at least partially; for instance aimedical.jp, rengarden.com, ns500758.ns500759.ns500698.ns500698.ns500698.ns500735.ns500698.ns500698.ns500735.ns500708.ns500698.ns500576.ns500698.ns500708.ns500619.ns500652.trackreceptor.com, ns500758.ns500759.ns500698.ns500698.ns500758.ns500736.ns500736.ns500735.ns500735.ns500576.ns500576.ns500619.ns500619.trackreceptor.com and ns500742.ns500731.ns500731.ns500754.ns500705.ns500671.ns500688.ns500704.ns500666.ns500291.ns500131.lustychickser.com.
these mail servers are commonly used alongside aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IPs:
Host aspmx.l.google.com has IPs 2607:f8b0:4004:c19::1b and 172.253.62.27.
Host alt1.aspmx.l.google.com has IPs 2607:f8b0:4003:c30::1b and 74.125.27.26.
Host alt2.aspmx.l.google.com has IPs 2607:f8b0:4001:c70::1a and 192.178.209.26.
Host alt3.aspmx.l.google.com has IPs 2607:f8b0:4024:c0d::1b and 192.178.152.26.
Host alt4.aspmx.l.google.com has IPs 2607:f8b0:4023:403::1a and 142.250.96.27.