Skip to content

Hostname

remotech.com

Last fetched

remotech.com resolves to 149.102.153.198, announced in 149.102.152.0/21 by CONTABO - Contabo GmbH in DE. remotech.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · remotech.comRouting diversity2.4/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/remotech.com

Resolution chain

IPv6 resolution

No AAAA record for remotech.com is recorded in WhisperGraph.

Attribution

contabo

ORIGIN_AS

WHOIS identity

Registrar
iana:1005
Registrant organisation
harley bird
Contact emails
dns@remotech.com, gdpr-masking@gdpr-masked.com

Subdomains

Subdomain
bns1.remotech.com
bns2.remotech.com
cpanel.remotech.com
cpcalendars.remotech.com
cpcontacts.remotech.com
ds1-dav.remotech.com
ds1.remotech.com
hweb1.remotech.com
link.remotech.com
mail.remotech.com
mx.remotech.com
n-8-n.remotech.com

Showing 12 of 18. View all subdomains →

Mail and authentication

Nameservers

  • bns1.remotech.com
  • bns2.remotech.com
  • ns1.thewebhostserver.com
  • ns2.thewebhostserver.com
  • ns3.thewebhostserver.com
  • ns4.thewebhostserver.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • remotech-com.mxguardian.net

SPF policy

  • a: remotech.com
  • mx: remotech.com
  • include: sender.zohobooks.com
  • include: spf-c.mailbaby.net
  • include: relay.mailchannels.net
  • ip: 149.102.153.198
  • ip: 91.232.125.142

Threat-feed evidence

History

Related pages

Pivot from remotech.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "remotech.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.